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

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)

Start by reproducing the breakpoint behavior with the Native Debug VSCode extension using rust-gdb, comparing the Debug Engine setting with VSCode's "Breakpoints in every file" setting. Done means breakpoints appear without enabling that global setting, but the issue does not name a repository file or test to guide further investigation.