[BUG] Stop caused by cpptools’ own -exec-interrupt (to insert a breakpoint while running) shows ‘Exception has occurred. Signal 0’ and doesn’t resume.
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- devtools
调研方向
Start by tracing how cppdbg handles GDB MI stop events with reason="signal-received" and how signal-name="0" is surfaced as an exception. The issue provides reproduction steps and debugger logs, but names no source files or tests; first reproduce with a 64-bit GDB debugging a 32-bit WOW64 process while inserting a breakpoint. Done means dynamic breakpoint insertion no longer shows a blocking false error for this stop.
由索引模型根据 Issue 内容生成。
描述
Environment
Environment:
- OS and Version: Windows 10 x64
- VS Code Version: 1.146.0
- C/C++ Extension Version: v1.32.2
- Debugger: GDB (both
x86_64-w64-mingw32-gdb18.1 andgdb-multiarch18.1 from MSYS2) - Target: 32-bit (i386) executable running under WOW64.
Bug Summary and Steps to Reproduce
When debugging a 32-bit (WOW64) process with a 64-bit GDB, the debugger halts and displays an "Exception has occurred. Signal 0" message. This happens when VS Code's cppdbg extension sends an -exec-interrupt command to pause the running process, typically to insert a new breakpoint.
The stop is reported by GDB with reason="signal-received" and signal-name="0" (an unknown signal), which the extension then surfaces as a blocking error dialog. The call stack is irrelevant to the cause; the program counter is simply wherever the thread happened to be (e.g., in a system or library function like SDL_LogCritical). This prevents adding breakpoints during an active debug session, as the user must manually click "Continue" to dismiss the false alarm every time.
To Reproduce:
- On Windows x64, configure
launch.jsonto use a 64-bit GDB (e.g.,C:/msys64/ucrt64/bin/gdb-multiarch.exe) to debug a 32-bit (i386) executable. - Start the debug session and let the program run.
- While the program is running, add a new breakpoint in a source file via the editor gutter.
- VS Code sends
-exec-interruptto pause the process. GDB responds with*stopped,reason="signal-received",signal-name="0". - The extension displays the "Exception has occurred. Signal 0" error.
Expected behavior:
The -exec-interrupt command should result in a normal, silent stop (e.g., reason="signal-received",signal-name="SIGINT"). The extension should not surface this as an exception or error to the user. The debugger should be ready for the subsequent -break-insert command without a blocking dialog.
Actual behavior:
The extension interprets GDB's signal-name="0" as a fatal error and surfaces an "Exception has occurred" dialog, halting the user's workflow.
Debugger Logs (engineLogging: true):
The log clearly shows the sequence: VS Code sends -exec-interrupt in response to a setBreakpoints request, and GDB replies with the spurious signal.
<-- C (setBreakpoints-12): {"command":"setBreakpoints","arguments":{"source":{"name":"Model.cpp",...},"lines":[174],...},"type":"request","seq":12}
1: (6400) <-1027-exec-interrupt
1: (6410) ->~"\nThread 1 stopped.\n"
1: (6415) ->*stopped,reason="signal-received",signal-name="0",signal-meaning="Signal 0",frame={addr="0x6c7be23f",func="SDL_LogCritical",from="...SDL2.dll",arch="i386"},thread-id="1",stopped-threads="all"
Additional context:
- The issue is not related to a specific C++ exception (a
catch throwcatchpoint hastimes="0"). - The issue is not related to SDL's thread-naming exception (
0x406D1388), as settingSDL_WINDOWS_DISABLE_THREAD_NAMING=1does not change the symptom. - The root cause is a known GDB bug where its Windows WOW64 support fails to correctly associate its own internal
DebugBreakProcesscall with the resultingSTATUS_BREAKPOINTexception, misreporting it asSignal 0. - This behavior is reproducible with both
gdbandgdb-multiarchfrom MSYS2. - A workaround is to set all breakpoints before starting the debug session, which avoids the
-exec-interrupt. However, this is not a fix for dynamic breakpoint insertion. - Relevant
launch.jsonconfiguration used:{ "type": "cppdbg", "request": "launch", "MIMode": "gdb", "miDebuggerPath": "C:/msys64/ucrt64/bin/gdb-multiarch.exe", "logging": { "engineLogging": true, "trace": true }, "setupCommands": [ ... ] } - An
ignoreFailuresor a "continue on signal 0" option in the extension could serve as a potential workaround for users unable to change their GDB version.
Debugger Configurations
see above
Debugger Logs
see above
Other Extensions
No response
Additional Information
No response
- 主要语言
- TypeScript
- 星标
- 6.2k
- 派生
- 1.7k
- 平均合并
- 1 天 17 小时
- 30 天内合并 PR
- 12
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/vscode-cpptools 的其他 Issue
-
Missing gcc __builtin_stdc_bit_width/floor/ceil signature makes intellisense wrongly report error 70未关闭
难度 2/5 1-3 小时 新手友好度 66/100
microsoft/vscode-cpptools#14874 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 65/100
microsoft/vscode-cpptools#14872 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 56/100
microsoft/vscode-cpptools#14871 ·
维护者通常 1 天内回复
-
Goto definition (F12) not working with (recursive) includes可能已有人在做 @Colengms 于 5 天前认领。 未关闭bug fixed Language Service
microsoft/vscode-cpptools#14868 · 2 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Support for new "!" file exclusion syntax可能已有人在做 @Colengms 于 5 天前认领。 未关闭bug Language Service
microsoft/vscode-cpptools#14867 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 microsoft/vscode-cpptools 的全部 Issue
相似的 Issue
-
area:cli area:security bug priority:medium
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
"code source" and "numerique.gouv" links: "new window" mention duplicated in the accessible name未关闭accessibility
难度 2/5 1-3 小时 新手友好度 72/100
numerique-gouv/lasuite-landingpage#315 ·
维护者通常 1 天内回复
-
needs:triage
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
HyeokjaeChoi/vaultme#585 ·
维护者通常 1 天内回复
-
enhancement priority/P2
难度 2/5 1-3 小时 新手友好度 72/100
beettlle/pi-smart-router#200 ·