Closed mehlian closed 3 months ago
Fixed my problem by using this setting in lldb:
settings set plugin.jit-loader.gdb.enable off
Now jit breakpoint signal is ignored and only mine breakpoints are honored.
Here is more detail about this: https://llvm.org/docs/DebuggingJITedCode.html
Discussed in https://github.com/vadimcn/codelldb/discussions/848
I have a similar problem when debugging an Android app - when a breakpoint is hit or a "step" is performed, the main thread is focused in vscode and I need to manually switch threads to continue debugging (main thread stop reason = jit-debug-register, second thread stop reason = breakpoint 1.1).
There is no problem when using lldb without vscode.Edit: After further investigation it looks like issue is with lldb (I'm not sure). Two threads are returning stop signal and first one is selected in vs code