cppdbg throws "Unable to find child property"
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- cpp, typescript, vscode
- Área
- developer-experience, devtools
Línea de trabajo
Empieza reproduciendo la secuencia con la ventana Variables oculta y, a continuación, inspecciona la solicitud dataBreakpointInfo y la llamada a evaluate relacionada en el adaptador de depuración cppdbg. Usa el registro GDB/MI proporcionado para rastrear la expresión vacía y la búsqueda de propiedades hijas. La tarea estará terminada cuando dataBreakpointInfo ya no produzca el error y aparezca el menú contextual del elemento observado.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment
Version: 1.106.0-insider (user setup)
Commit: 18d828e5d596e56b516fac7baa53e4b32cf087be
Date: 2025-11-04T05:03:04.572Z
Electron: 37.7.0
ElectronBuildId: 12597478
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Bug Summary and Steps to Reproduce
Bug Summary:
The cppdbg debugger adapter throws "Unable to find child property."
Refer: https://github.com/microsoft/vscode/issues/273721
Steps to reproduce:
- in vscode, open a c++ project
- set a breakpoint and start debugging to hit that
- hide the 'Variables' window
- reload the vscode
- start debugging again, add an variable in watch, right on the watched item.
the context menu doesn't show up due to thedataBreakpointInfo()call into cppdbg debugger adapter throws "Unable to find child property.
Debugger Configurations
{
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/out",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
]
}
Debugger Logs
<-- C (evaluate-18): {"command":"evaluate","arguments":{"expression":"","frameId":1000,"context":"hover","line":15,"column":0,"source":{"name":"main.cpp","path":"c:\\Users\\brchen\\repos\\test-cpp\\src\\main.cpp","sources":[],"checksums":[]}},"type":"request","seq":18}
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4390) <-1030-var-create - * \"\"\r\n"},"seq":690}
1: (4390) <-1030-var-create - * ""
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4399) ->1030^error,msg=\"-var-create: unable to create variable object\"\r\n"},"seq":692}
1: (4399) ->1030^error,msg="-var-create: unable to create variable object"
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4399) 1030: elapsed time 9\r\n"},"seq":694}
1: (4399) 1030: elapsed time 9
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4399) ->(gdb)\r\n"},"seq":696}
1: (4399) ->(gdb)
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4400) ->&\"\\n\"\r\n"},"seq":698}
1: (4400) ->&"\n"
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4400) ->^done\r\n"},"seq":700}
1: (4400) ->^done
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (4400) ->(gdb)\r\n"},"seq":702}
1: (4400) ->(gdb)
--> R (evaluate-18): {"type":"response","request_seq":18,"success":false,"command":"evaluate","message":"Evaluation error","body":{},"seq":704}
<-- C (dataBreakpointInfo-19): {"command":"dataBreakpointInfo","arguments":{"name":"s.x","frameId":1000},"type":"request","seq":19}
--> R (dataBreakpointInfo-19): {"type":"response","request_seq":19,"success":false,"command":"dataBreakpointInfo","message":"Unable to get info for data breakpoint. Unable to find child property.","body":{},"seq":707}
Other Extensions
No response
Additional Information
No response
- Lenguaje dominante
- TypeScript
- Estrellas
- 6.2k
- Forks
- 1.7k
- Merge medio
- 14 h 46 min
- PR fusionados (30 d)
- 61
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/vscode-cpptools
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
microsoft/vscode-cpptools#14787 ·
-
[Bug] cpptools fails to start on Ubuntu ARM64 due to missing execute permissions on shared libraries Abiertobug fixed Language Service regression
microsoft/vscode-cpptools#14779 · 1 asignado ·
-
Language Service more info needed
microsoft/vscode-cpptools#14778 · 1 comentario · 1 asignado ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 64/100
microsoft/vscode-cpptools#14769 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
microsoft/vscode-cpptools#14768 · 1 comentario ·
Todos los issues de microsoft/vscode-cpptools
Issues similares
-
Browser Waiting for: Product Owner
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
getsentry/sentry-javascript#24577 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
agilepathway/label-checker#640 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
copse-dev/agent-pane#2953 ·
-
[aw] Upgrade available Abiertoagentic-workflows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
anomalyco/models.dev#7701 ·