debug crashes while debugging

Nobody has claimed this yet.

Type: Performance Issue

when you add a expression to the watch sometimes debug crashes and gdb is still running

Extension version: 1.23.4
VS Code version: Code - Insiders 1.97.0-insider (f5782f528629d4200a964cc652055a4da43a7eb1, 2025-01-24T05:04:36.365Z)
OS version: Windows_NT x64 10.0.27774
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	7.84GB (1.34GB free)
Process Argv	--crash-reporter-id d300ccb5-f585-43c6-995d-6505aed890c2
Screen Reader	no
VM	0%

Process Info

CPU %	Mem MB	   PID	Process
    0	    81	  6804	code-insiders main
    0	    15	   412	   utility-network-service
    0	    73	  5132	shared-process
    0	    95	 15064	     "C:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" "c:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\bootstrap-fork" ms-vscode.cppdbg "{\"common.vscodemachineid\":\"c0947ecf06aa2d92d64dbe20b32e88885ec7c7adefd3dce74b34e50491184a05\",\"common.vscodesessionid\":\"4637197f-9c84-4dcd-887b-44bc7091b6af1737855769615\"}" 0c6ae279ed8443289764825290e4f9e2-1a736e7c-1324-4338-be46-fc2a58ae4d14-7255
    1	   386	  5240	window [1] (641.cpp - a - Visual Studio Code - Insiders)
    0	    33	  8036	ptyHost
    0	    12	  6840	     "C:\Program Files\PowerShell\7\pwsh.exe" -noexit -command "try { . \"c:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1\" } catch {}"
    0	     3	  9368	     conpty-agent
    0	    72	 14436	     "C:\Program Files\PowerShell\7\pwsh.exe" -noexit -command "try { . \"c:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1\" } catch {}"
    0	    21	 19600	       "C:\Users\123\.vscode-insiders\extensions\ms-vscode.cpptools-1.23.4-win32-x64\debugAdapters\bin\WindowsDebugLauncher.exe" --stdin=Microsoft-MIEngine-In-utklzvlb.gdv --stdout=Microsoft-MIEngine-Out-3kgekeb0.bic --stderr=Microsoft-MIEngine-Error-jlona0hf.2xe --pid=Microsoft-MIEngine-Pid-2muaks2n.k1z --dbgExe=C:\msys64\mingw64\bin\gdb.exe --interpreter=mi
    0	    32	 22640	         "C:\msys64\mingw64\bin\gdb.exe" --interpreter=mi 
    0	   119	  6992	           "C:\Users\123\Desktop\a\641.exe"   
    0	     2	 15568	     conpty-agent
    0	     3	  9268	   crashpad-handler
    0	   142	  9556	   gpu-process
    1	   392	 14660	extensionHost [1]
    0	    52	  3492	     c:\Users\123\.vscode-insiders\extensions\ms-vscode.cpptools-1.23.4-win32-x64\debugAdapters\bin\OpenDebugAD7.exe
    0	     7	 11576	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    10	 11344	     "C:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" "c:\Users\123\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=14660
    0	     7	 17284	     electron-nodejs (eslintServer.js )
    0	     9	 17452	     electron-nodejs (languageServer.js )
    0	    75	 17884	     c:\Users\123\.vscode-insiders\extensions\ms-vscode.cpptools-1.23.4-win32-x64\bin\cpptools.exe
    0	     0	  9488	       "c:\Users\123\.vscode-insiders\extensions\ms-vscode.cpptools-1.23.4-win32-x64\bin\cpptools.exe"
    0	   181	 17648	         c:\Users\123\.vscode-insiders\extensions\ms-vscode.cpptools-1.23.4-win32-x64/bin/cpptools-srv.exe 17884 {9189A6D8-55DC-49C5-AB24-DAB8E497A392}
    0	     1	  2684	           C:\WINDOWS\system32\conhost.exe 0x4
    0	     1	 17908	       C:\WINDOWS\system32\conhost.exe 0x4
    0	     7	 18052	     electron-nodejs (server.js )
    0	    22	 16360	fileWatcher [1]

Workspace Info

|  Window (641.cpp - a - Visual Studio Code - Insiders)
|    Folder (a): 1302 files
|      File types: cpp(641) exe(641) json(8) vsidx(2) wsuo(1) db(1) bin(1)
|                  sqlite(1)
|      Conf files: launch.json(1) settings.json(1) tasks.json(1)
|      Launch Configs: cppdbg;

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31179977
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupytercf:31046870
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
c3hdf307:31184662
6074i472:31201624
dwoutputs:31217127
6e63a538:31218797
9064b325:31222308
copilot_t_ci:31222730
58g5h367:31224756

Reproduce the crash by adding a watch expression while debugging the C++ program described in the report, using the WindowsDebugLauncher.exe, OpenDebugAD7.exe, and GDB processes as the debugging entry points. No source file or test is named, so first locate the watch-expression handling in the debug adapter and capture why the extension crashes while GDB remains running. Done means the watch operation no longer crashes the extension and the debugger process is handled correctly.

Written by the indexing model from the issue text.

Description

Contributor guide

First steps

Research direction

Assessment