vadimcn / codelldb

A native debugger extension for VSCode based on LLDB
https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb
MIT License
2.42k stars 237 forks source link

Extension is crashing just after hitting a breakpoint #1111

Open jovanat455 opened 3 weeks ago

jovanat455 commented 3 weeks ago

OS: Linux (remote via Remote SSH) VSCode version: 1.90.0 CodeLLDB version: 1.10.0 Compiler: gcc 11.4.0 Debuggee: Executable binary

I am debugging remotely on a Windows device by running the executable and attaching to it. When I run the debugger without any breakpoints, the session finishes successfully. However, when I set a breakpoint, the extension crashes with the error: Debug adapter exit code=255 (0xff), signal=null immediately after hitting the breakpoint. This happens every time I run it. If I use LLDB directly from the command line, everything works correctly; I am able to hit a breakpoint and run a debugging session.

Initial debug configuration: { name: 'TestCLI (c++)', type: 'lldb', request: 'launch', program: '/test_cli', args: [ '-config_query', '/config_test.yml' ], cwd: '/tests', initCommands: [ 'settings set target.disable-aslr false' ], logging: { engineLogging: true, trace: true, traceResponse: true }, externalConsole: true, __configurationTarget: 5 } Resolved debug configuration: { name: 'TestCLI (c++)', type: 'lldb', request: 'launch', program: '/test_cli', args: [ '-config_query', '/config_test.yml' ], cwd: '/tests', initCommands: [ 'settings set target.disable-aslr false' ], logging: { engineLogging: true, trace: true, traceResponse: true }, externalConsole: true, configurationTarget: 5, relativePathBase: '/project/plugin', _adapterSettings: { displayFormat: 'auto', showDisassembly: 'auto', dereferencePointers: true, suppressMissingSourceFiles: true, evaluationTimeout: 5, consoleMode: 'commands', sourceLanguages: null, terminalPromptClear: null, evaluateForHovers: true, commandCompletions: true, reproducer: false } } Received signal: SIGSEGV 0: codelldb::hook_crashes::handler 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: _ZN4lldb7SBFrame18EvaluateExpressionEPKcRKNS_19SBExpressionOptionsE 40: _ZN4lldb7SBFrame18EvaluateExpressionEPKc 41: 42: 43: _PyObject_Call 44: _PyEval_EvalFrameDefault 45: 46: _PyFunction_Vectorcall 47: 48: 49: _PyEval_EvalFrameDefault 50: _PyFunction_Vectorcall 51: 52: _PyEval_EvalFrameDefault 53: 54: _PyFunction_Vectorcall 55: 56: _PyEval_EvalFrameDefault 57: 58: PyEval_EvalCode 59: 60: 61: 62: _PyEval_EvalFrameDefault 63: 64: _PyFunction_Vectorcall 65: 66: _PyEval_EvalFrameDefault 67: _PyFunction_Vectorcall 68: 69: 70: 71: 72: codelldb::python::PythonInterface::evaluate 73: codelldb::debug_session::variables::::evaluate_expr_in_frame 74: codelldb::debug_session::variables::::handle_evaluate_expression 75: codelldb::debug_session::variables::::handle_evaluate 76: codelldb::debug_session::DebugSession::handle_request 77: tokio::runtime::task::core::Core<T,S>::poll 78: tokio::runtime::task::harness::Harness<T,S>::poll 79: tokio::task::local::LocalSet::tick 80: std::thread::local::LocalKey::with 81: ::poll 82: codelldb::run_debug_session::{{closure}} 83: tokio::runtime::context::blocking::BlockingRegionGuard::block_on 84: tokio::runtime::context::runtime::enter_runtime 85: codelldb::debug_server 86: codelldb::main 87: std::sys_common::backtrace::rust_begin_short_backtrace 88: std::rt::lang_start::{{closure}} 89: std::rt::lang_start_internal 90: main 91: libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 92: libc_start_main_impl at ./csu/../csu/libc-start.c:392:3 93: _start

Debug adapter exit code=255 (0xff), signal=null.