CodeLLDB catching an unexpected interrupt.

[jwildstr-ibm]

OS: Red Hat Enterprise Linux 8.10
VSCode version: 1.120.0
CodeLLDB version: 1.11.4, also happened with 1.12.2
Compiler: rust, 1.94.1 toolchain
Debuggee: compiled executable

Trying to set breakpoints inside a deep code path. Breakpoint will hit once or twice, and then codelldb is crashing with a keyboard interrupt

(Semi-)Verbose log

I've trimmed the log to ensure that no internal information could be leaked. but since this seems to tie to the interrupt, this feels like it should be sufficient.

[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

[vadimcn]

It isn't crashing, this is CodeLLDB interrupting execution of the Python data formatter which got stuck.

[jwildstr-ibm]

So does that mean that this is an issue in the python component of LLDB? I'm not sure where to report this issue, since it's clearly a problem (just not with CodeLLDB)

[vadimcn]

The data formatter is loaded from your active Rust toolchain, so you should report it to them.