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
MinGW 13.2.0 toolchain's GDB (version 11.2), when run through the C/C++ Debug Adapter, cannot force the program to break without a defined breakpoint.
#13191
Open
tfinnegan937 opened this issue
Jan 24, 2025
· 1 comment
The nature of this work is sensitive, and the amount of information that I can provide about our codebase is limited. I would be happy to build smaller examples for the purposes of debugging this, however.
The text was updated successfully, but these errors were encountered:
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
OS and version:
Windows 10 22H2 Build Version 19045.5371
VS Code:
1.96.3
C/C++ extension:
1.22.11
GDB / LLDB version:
GNU gdb (GDB) 11.2 (Provided with the MinGW version below.
https://github.com/niXman/mingw-builds-binaries/releases/tag/13.2.0-rt_v11-rev1
(This is an official build pointed to by MinGW's downloads page, under the MinGW-w64 Builds heading https://www.mingw-w64.org/downloads/)
Bug Summary and Steps to Reproduce
Bug Summary:
The bugger starts successfully, but then the program refuses to break unless a breakpoint is set prior to execution. The "pause" button does not work.
Why are we using MinGW on Windows? We're doing some work with an analysis tool that only supports GCC. Switching to MSVC is not a viable workaround.
Steps to reproduce:
Debugger Configurations
Debugger Logs
Other Extensions
Additional Information
The nature of this work is sensitive, and the amount of information that I can provide about our codebase is limited. I would be happy to build smaller examples for the purposes of debugging this, however.
The text was updated successfully, but these errors were encountered: