VSCode/CodeLLDB crash on 1.94.1

editors and IDEs
1

I've been trying to debug a large work project that I've previously used VSCode successfully on. We recently updated to 1.94, and I'm having issues with CodeLLDB. I asked there, and they told me it wasn't them, it was Rust. Stack trace on crash is

[DEBUG codelldb::dap_codec] --> {"command":"variables","arguments":{"variablesReference":1022},"type":"request","seq":23}
[DEBUG codelldb::dap_codec] --> {"command":"stackTrace","arguments":{"threadId":3431995,"startFrame":1,"levels":19},"type":"request","seq":24}
[DEBUG codelldb::dap_codec] --> {"command":"continue","arguments":{"threadId":3431995},"type":"request","seq":25}
[INFO  codelldb::python] Sending interrupt to Python interpreter
Traceback (most recent call last):
  File "/home/jwildstr/.rustup/toolchains/1.94.1-x86_64-unknown-linux-gnu/lib/rustlib/etc/lldb_lookup.py", line 124, in synthetic_lookup
    return StdHashMapSyntheticProvider(valobj, _dict, show_values=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/jwildstr/.rustup/toolchains/1.94.1-x86_64-unknown-linux-gnu/lib/rustlib/etc/lldb_providers.py", line 1146, in __init__
    self.update()
  File "/home/jwildstr/.rustup/toolchains/1.94.1-x86_64-unknown-linux-gnu/lib/rustlib/etc/lldb_providers.py", line 1216, in update
    ).GetValueAsUnsigned()
      ^^^^^^^^^^^^^^^^^^^^
  File "/home/jwildstr/.vscode/extensions/vadimcn.vscode-lldb-1.11.4/lldb/lib/lldb-python/lldb/__init__.py", line 15431, in GetValueAsUnsigned
    return _lldb.SBValue_GetValueAsUnsigned(self, *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<string>", line 4, in signal_handler
KeyboardInterrupt

Anyone have any idea if I can fix this locally, or, if not, how I get it fixed in Rust?

2

The CodeLLDB discussion is CodeLLDB catching an unexpected interrupt. · Issue #1392 · vadimcn/codelldb · GitHub

3

You can report issues at Issues · rust-lang/rust · GitHub. Include the statement from the other thread that this indicates it is hanging. You should also provide code that can cause the problem when debugged.

4

I'm not sure I can include code. I'll keep trying, but this is a large project for work, so I can't just publish it. For now, I'll open the issue, though.