[Possible Bug]: Breakpoints not appearing with `Native Debugger` vscode extension. Cannot set as debug engine.

[AZMCode]

Background

I'm currently switching debuggers from rust-lldb to rust-gdb. There are no extensions for rust-gdb that I'm aware of, so piecing together several extensions and scripts I have managed to compile my crate, identify the output binary, and debug it using Native Debug, itself using rust-gdb as the backend.

However, I can no longer place breakpoints in my program. I've been searching around for the culprit, and the only lead I have so far is this extension's "Debug Engine" setting, which mysteriously seems restricted to two extensions, despite there being more gdb/lldb debug extensions out there. Is there any way I can bypass this without enabling VSCode's Breakpoints in every file setting?

(Note: My setup works flawlessly if I do enable that setting)

[lnicola]

We'd probably need to add other debug engines here: https://github.com/rust-analyzer/rust-analyzer/blob/master/editors/code/src/debug.ts#L63-L66

[AZMCode]

Perhaps it would be best to add support for all known debuggers for both GDB and LLDB

[lnicola]

Do you want to give it a try?

[AZMCode]

Perhaps later. Currently my devel laptop is out of service, but when it's fixed I might come back to it.

[AZMCode]

Alright, I'm back on, and sadly I forgot about this for a bit. However, I am stumbling into this problem again, and might dedicate some time to help fixing this. On it.