-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rust synth summary KeyError #949
Comments
What exactly do you mean by "print a variable"? Can you please provide a verbose log? |
Thanks for the patience and not closing the issue. I pivoted over to another project for a while.
Using nvim-dap-ui:
Beautiful, this is great, thanks.
FWIW, I am running in nvim. I was able to replicate the verbose logging in VSCode by setting codelldb/extension/novsc/adapter.ts Line 42 in f4b6ad6
|
I was running into this too, and here's my findings for my case: Line 115 in 05502bf
tries to retrieve an Index of a child with name, using the LLDB function where we can see that There is no check for this error value before Line 116 in 05502bf
Leading it to try to index on an error code. In my case, the parent value ( I thought this might be generalised over all Enums because of this, but user-defined enums seem to be perfectly fine. It might be that it's enums with generics, but I haven't had the time to investigate that yet. |
@vadimcn because extra info, for good measure. |
Workaround Update (@erichulburd):
(or something that equivalently matches any FQN of This means it should probably be resolved in https://github.com/rust-lang/rust/blob/master/src/etc/lldb_commands rather than it being a codelldb issue. I will look into it a bit more, and then likely make an issue and PR there |
Alright, one more. Been at this all day: The snippets me and @erichulburd have been using are only for I think this ticket can be closed as the issue boils down to "Using configs meant for a different tool breaks this tool" |
OS:
VSCode version:
I am actually using nvim:
CodeLLDB version: 1.9.2
Compiler
Debugee
Rust binary. A silly, simple program:
The Problem
While I am able to attach to the debugger, set breakpoints, and print variable names, on startup and each time I print a variable, I get Python stacktrace from a
KeyError
onget_synth_summary
informatters/rust.py
for obj id4294967295
.Also, it may be useful to know that I am following the snippets in the nvim-dap Wiki for Rust lldb-vscode.
The text was updated successfully, but these errors were encountered: