-
Notifications
You must be signed in to change notification settings - Fork 256
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
Cannot read property 'id' of undefined #641
Comments
This extension always worked with the msvc toolchain... right? I didn't have the GNU installed 5 days ago and it used to work just fine. Because I just installed the nightly gnu toolchain, set it as default, and it's working now. |
Probably the same issue as #633. You can either roll back to an earlier nightly, or use the -gnu compilation target, which is what I'd recommend anyway. The problem with onChangedActiveDebugSession seems to be a real bug, as my code does not expect
This could be the difference between -msvc and -gnu targets. Enums are encoded very differently in the debug info between these two. |
Thanks, I'll keep using the gnu toolchain. |
OS: Windows 11 Pro 21H2 build 22000.493 The same thing happened to me. I struggled with it before seeing this report. I switched to stable-x86_64-pc-windows-gnu did a clean and rebuild. PDB files were not present and the debugger hit breakpoints. I had not collected the verbose log, so switched back to stable-x86_64-pc-windows-msvc, did a clean and rebuild. A PDB file was back and the debugger still hit breakpoints. Hmm |
Fixed in v1.7.0 |
OS: Windows 11 Pro 21H2 build 22000.493
VSCode version: 1.64.1
CodeLLDB version: 1.16.10
Compiler: rustc 1.60.0-nightly (0c292c966 2022-02-08) (happens on 1.56 as well)
Debuggee: Windows executable (nightly-x86_64-pc-windows-msvc)
When I hit the green play button, the executable runs but the breakpoints are not hit. It started happening yesterday.
In the developer tools console, I see an error:
I believe this error happens in this function: https://github.com/vadimcn/vscode-lldb/blob/6e9d5e5ea940aae1dde4388b2fd0ca8901c810f4/extension/modulesView.ts#L88
Unfortunately I failed to debug the extension myself, so I can't check any further.
I tried installing a slightly older version of vscode (1.63) but it still happens.
I can't recall if I changed something in my system to cause this.
Extension crash
Verbose log
The text was updated successfully, but these errors were encountered: