Received signal: SIGSEGV

[Spongman]

OS: rocky9 (via remote-wsl)
VSCode version: 1.89.1
CodeLLDB version: v1.10.0
Compiler: gcc version 13.1.1 20230614
Debuggee: x86_64-linux-gnu

just hovering over various aymbols while debugging

Received signal: SIGSEGV
   0: codelldb::hook_crashes::handler
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: <unknown>
  35: <unknown>
  36: <unknown>
  37: <unknown>
  38: <unknown>
  39: _ZN4lldb7SBFrame18EvaluateExpressionEPKcRKNS_19SBExpressionOptionsE
  40: _ZN4lldb7SBFrame18EvaluateExpressionEPKc
  41: <unknown>
  42: <unknown>
  43: _PyObject_Call
  44: _PyEval_EvalFrameDefault
  45: <unknown>
  46: _PyFunction_Vectorcall
  47: <unknown>
  48: <unknown>
  49: _PyEval_EvalFrameDefault
  50: _PyFunction_Vectorcall
  51: <unknown>
  52: _PyEval_EvalFrameDefault
  53: <unknown>
  54: _PyFunction_Vectorcall
  55: <unknown>
  56: _PyEval_EvalFrameDefault
  57: <unknown>
  58: PyEval_EvalCode
  59: <unknown>
  60: <unknown>
  61: <unknown>
  62: _PyEval_EvalFrameDefault
  63: <unknown>
  64: _PyFunction_Vectorcall
  65: <unknown>
  66: _PyEval_EvalFrameDefault
  67: _PyFunction_Vectorcall
  68: <unknown>
  69: <unknown>
  70: <unknown>
  71: <unknown>
  72: codelldb::python::PythonInterface::evaluate
  73: codelldb::debug_session::variables::<impl codelldb::debug_session::DebugSession>::evaluate_expr_in_frame
  74: codelldb::debug_session::variables::<impl codelldb::debug_session::DebugSession>::handle_evaluate_expression
  75: codelldb::debug_session::variables::<impl codelldb::debug_session::DebugSession>::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<T>::with
  81: <tokio::task::local::LocalSet as core::future::future::Future>::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
  92: __libc_start_main_alias_1
  93: _start
Debug adapter exit code=255 (0xff), signal=null.

[Spongman]

does anyone know a workaround for this? unfortunately, it makes this extension almost unusable for debugging C++ code since just moving the cursor over a source file causes it to crash randomly.

[vadimcn]

Probably a lldb bug. I've upgraded to LLDB v19 in the last version, please try it. This also might help