Closed kylewlacy closed 1 year ago
Sounds similar to https://github.com/microsoft/vscode/issues/181485
Based on the VS Code discussions, I gave this a test in VS Code Insiders as well since there was already a proposed fix in place. I can confirm that I don't have this issue in VS Code Insiders, so it seems like this was an upstream issue! Since the fix is already available on the Insiders channel, plus reverting to VS Code 1.77 would also work as a workaround, I'm going to close this issue because it doesn't seem like there's anything to do on CodeLLDB's side.
OS: Ubuntu 22.04 via WSL remote (Windows 11) VSCode version: 1.78.1 CodeLLDB version: 1.9.1 (also tested against 1.9.0) Compiler: clang 15.0.6 Debuggee: Bare metal aarch64 assembly, via qemu + gdb-remote
I've been using CodeLLDB while debugging a small bare-metal aarch64 side project. A little over a week ago, I got my debugging setup working smoothly, and thoroughly tested setting breakpoints, continuing/pausing execution, setting watch expressions, and stepping in/out/over lines of code. I put the project on pause for a few days, but I found that when I came back to it, my debugging setup had broken. In the meantime, I believe both CodeLLDB and VS Code had been updated, but I don't believe I had updated any other relevant packages on my system (but I may be wrong about that). I can't seem to figure out if there's some setting I need to change to get things working again, but I believe this could be a bug in CodeLLDB itself (maybe caused by an upstream VSCode change)? The relevant log line I see now is the following (full log output also provided):
I also created a small example repo that should reliably reproduce this issue here: https://github.com/kylewlacy/codelldb-demo-qemu (requires
qemu-system-aarch64
,clang
,lld
,objcopy
, andmake
).Steps to reproduce
asm/raspi3/boot.S:6
0x00000000
(this is expected).Expected outcome
"Continue" should have continued debugging, or "Step over" should have jumped over a single asm instruction. Either button previously had worked exactly as expected.
Actual outcome
Neither "Continue" nor "Step over" seem to do anything in the debug session. Clicking both is what seems to lead to the above log message, for some reason.
Standard log output
Verbose log