You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ms-vscode.cpptools
Version
1.24.5
Last Updated
2025-04-18, 08:14:49
OS and version of remote machine (if applicable):
Running VSCode inside WSL w/Ubuntu 22.04
GDB / LLDB version:
GNU gdb (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16)) 10.1.90.20201028-git
Bug Summary and Steps to Reproduce
Bug Summary:
Using WSL + Ubuntu 22.04
I am building an ARM TFA project and attempting to debug it under QEMU.
Everything works fine if I launch QEMU and GDB from the command line.
Now I am trying to launch GDB under VS Code to get a better debugging experience (source & variable display windows)
launch.gdb has all the instructions necessary to attach to my GDB and set my interesting breakpoints.
Notably launch.gdb does NOT continue execution and QEMU is setup to waiting for the debugger to attach AND continue program execution manually. This is because the part I am trying to debug is in the early boot loader.
I created a tasks.json entry to launch QEMU and that works fine. However, I cannot seem to find a configuration for launch.json which will cause the debugger to attach and then stop.
for example, the normal command-line GDB output is as simple as this:
Reading symbols from /home/.../AARCH64/bl2.elf...
0x0000000080000000 in ?? ()
Breakpoint 1 at 0x80101e28: file io_storage.c, line 63.
Breakpoint 2 at 0x801008e4: file io_storage.c, line 212.
Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
(gdb)
However, when I use VSCode, QEMU starts running and goes past the part of the code I want to debug.
Reproducing this is a bit difficult because it requires a qemu and TFA build setup, but I have attached the launch.json & debug console output. Hopefully there will be some clue here.
Appreciate any help
Debugger Configurations
(NOTE: using request:attach doesn't seem to solve my problem either).
Thank you for reporting this issue. We’ll let you know if we need more information to investigate it. Additionally, if you're working with GDB/LLDB, please note that the code is open source at https://github.com/microsoft/MIEngine/wiki/Contributing-Code . Your contributions are always welcome and appreciated.
Environment
VS Code version info:
Version: 1.100.0-insider (system setup)
Commit: 1b000ef82b3c3082833f6b04e050bc0e4e12ae3b
Date: 2025-04-18T05:31:28.011Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26200
C/C++ extension:
ms-vscode.cpptools
Version
1.24.5
Last Updated
2025-04-18, 08:14:49
OS and version of remote machine (if applicable):
Running VSCode inside WSL w/Ubuntu 22.04
GDB / LLDB version:
GNU gdb (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16)) 10.1.90.20201028-git
Bug Summary and Steps to Reproduce
Bug Summary:
Using WSL + Ubuntu 22.04
I am building an ARM TFA project and attempting to debug it under QEMU.
Everything works fine if I launch QEMU and GDB from the command line.
Now I am trying to launch GDB under VS Code to get a better debugging experience (source & variable display windows)
The GDB command line I use is very simple:
/home/.../bin/aarch64-none-elf-gdb -x launch.gdb /home/.../AARCH64/bl2.elf
launch.gdb has all the instructions necessary to attach to my GDB and set my interesting breakpoints.
Notably launch.gdb does NOT continue execution and QEMU is setup to waiting for the debugger to attach AND continue program execution manually. This is because the part I am trying to debug is in the early boot loader.
I created a tasks.json entry to launch QEMU and that works fine. However, I cannot seem to find a configuration for launch.json which will cause the debugger to attach and then stop.
for example, the normal command-line GDB output is as simple as this:
However, when I use VSCode, QEMU starts running and goes past the part of the code I want to debug.
Reproducing this is a bit difficult because it requires a qemu and TFA build setup, but I have attached the launch.json & debug console output. Hopefully there will be some clue here.
Appreciate any help
Debugger Configurations
(NOTE: using request:attach doesn't seem to solve my problem either).
Debugger Logs
Other Extensions
No response
Additional Information
The text was updated successfully, but these errors were encountered: