Open adrebit opened 3 years ago
Looks like it crashes in the guts of LLDB... Probably picked up a new bug along with LLDB 13 😞
OS: Mac OSX Big sur 11.5.2 VSCode version: 1.60.0 (m1) CodeLLDB version: v1.6.6 Compiler: Gcc 10.1 Debugger: Native c++ executable
debug the program in a remote container (ubuntu 18.04, x86_64) have a similar issue, but I have a python runtime error.
Traceback (most recent call last):
File "/root/.vscode-server/extensions/vadimcn.vscode-lldb-1.6.6/adapter/codelldb.py", line 152, in evaluate
value = evaluate_in_context(pycode, is_simple_expr, context)
File "/root/.vscode-server/extensions/vadimcn.vscode-lldb-1.6.6/adapter/codelldb.py", line 284, in evaluate_in_context
return eval(code, eval_globals, eval_locals)
File "<input>", line 1, in <module>
File "/root/.vscode-server/extensions/vadimcn.vscode-lldb-1.6.6/adapter/value.py", line 40, in __getattr__
raise AttributeError("Attribute '%s' is not defined" % name)
AttributeError: Attribute 'GetSize' is not defined
@zhen8838 not sure it's the same, you seem to be crashing in command completion. This can be disabled via "lldb.commandCompletions" setting.
@vadimcn OK, when disabling it, never crashing again.
same here
OS: Mac OSX BigSur 11.6 VSCode version: 1.61.2 CodeLLDB version: v1.6.8 Compiler: Apple Clang 13.0.0 Debuggee: Native c++ executable
OS: Mac OSX Catalina 10.15.7 VSCode version: 1.60.0 (Universal) CodeLLDB version: v1.6.6 Compiler: Apple Clang 11.0.3 Debuggee: Native c++ executable
Since upgrading to v1.6.6 I see the error message
Oops! The debug adapter has terminated abnormally
pop up seemingly randomly which causes the debugger to abort and the program being debugged to run to completion. I have seen this when stepping over, in or out of functions and when hovering over variables to see their values. I have not been able to identify a common cause but it seems to have a change to happen when I interact with the debugger in any way.Verbose log - crash when stepping out of a function (mildly redacted with `@@@` for some private code specifics)
One more data point - I seem to get a different log message when verbose logging is disabled - not sure if this is a helpful clue or not 😄
Non-verbose log