microsoft / microsoft/vscode-cpptools
Error launching debugger in vscode
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
Environment
- OS and version: Arch Linux (rolling release)
- VS Code: 1.84.2 (flatpack)
- C/C++ extension: 1.18.5
- OS and version of remote machine (if applicable): N/A
- GDB / LLDB version: GNU gdb (GDB) 13.2
Bug Summary and Steps to Reproduce
Bug Summary:
I have a launch profile for debugging my C application. When i try to launch the debugger from vscode, i get the following error:
/bin/sh: /tmp/Microsoft-MIEngine-Cmd-mgfsu0jc.0b0: Datei oder Verzeichnis nicht gefunden
Launching the application without debugging works without any issues.
Steps to reproduce:
- Run Debugger with my launch profile in my environment (see debugger configurations)
- Error occurs
Debugger Configurations
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "(Linux) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/bin/testbed",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}/bin/",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "/usr/bin/gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
//"preLaunchTask": "C/C++: g++ build active file"
}
]
}
Debugger Logs
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (42) LaunchOptions{\"name\":\"(Linux) Launch\",\"type\":\"cppdbg\",\"request\":\"launch\",\"program\":\"/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin/testbed\",\"args\":[],\"stopAtEntry\":false,\"cwd\":\"/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin/\",\"environment\":[],\"externalConsole\":false,\"MIMode\":\"gdb\",\"miDebuggerPath\":\"/usr/bin/gdb\",\"setupCommands\":[{\"description\":\"Enable pretty-printing for gdb\",\"text\":\"-enable-pretty-printing\",\"ignoreFailures\":true}],\"logging\":{\"engineLogging\":true,\"trace\":true,\"traceResponse\":true},\"__configurationTarget\":6,\"__sessionId\":\"150423f7-322e-4921-8783-6fd71cd4c102\"}\n"},"seq":2}
1: (42) LaunchOptions{"name":"(Linux) Launch","type":"cppdbg","request":"launch","program":"/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin/testbed","args":[],"stopAtEntry":false,"cwd":"/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin/","environment":[],"externalConsole":false,"MIMode":"gdb","miDebuggerPath":"/usr/bin/gdb","setupCommands":[{"description":"Enable pretty-printing for gdb","text":"-enable-pretty-printing","ignoreFailures":true}],"logging":{"engineLogging":true,"trace":true,"traceResponse":true},"__configurationTarget":6,"__sessionId":"150423f7-322e-4921-8783-6fd71cd4c102"}
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (68) DbgCmd:echo $$ > /tmp/Microsoft-MIEngine-Pid-j1r52o12.jdl ; cd \"/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin\" ; DbgTerm=`tty` ; set -o monitor ; trap 'rm \"/tmp/Microsoft-MIEngine-In-4khxyljf.1ye\" \"/tmp/Microsoft-MIEngine-Out-vx5yyjue.xz3\" \"/tmp/Microsoft-MIEngine-Pid-j1r52o12.jdl\" \"/tmp/Microsoft-MIEngine-Cmd-1pcdnrjx.frq\"' EXIT ; \"/usr/bin/gdb\" --interpreter=mi --tty=$DbgTerm < \"/tmp/Microsoft-MIEngine-In-4khxyljf.1ye\" > \"/tmp/Microsoft-MIEngine-Out-vx5yyjue.xz3\" & clear; pid=$! ; echo $pid > \"/tmp/Microsoft-MIEngine-Pid-j1r52o12.jdl\" ; wait $pid; \n"},"seq":4}
1: (68) DbgCmd:echo $$ > /tmp/Microsoft-MIEngine-Pid-j1r52o12.jdl ; cd "/home/nils/ssdbig/Projekte/PublicTransportGameEngine/bin" ; DbgTerm=`tty` ; set -o monitor ; trap 'rm "/tmp/Microsoft-MIEngine-In-4khxyljf.1ye" "/tmp/Microsoft-MIEngine-Out-vx5yyjue.xz3" "/tmp/Microsoft-MIEngine-Pid-j1r52o12.jdl" "/tmp/Microsoft-MIEngine-Cmd-1pcdnrjx.frq"' EXIT ; "/usr/bin/gdb" --interpreter
Other Extensions
No response
Additional Information
No response
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia con il percorso di avvio del debugger per l'estensione C/C++ e con il comando MIEngine mostrato nei Debugger Logs, riproducendo la configurazione di avvio su Arch Linux con GDB. Il lavoro è completato quando l'applicazione C configurata si avvia sotto il debugger senza l'errore relativo al file di comandi temporaneo mancante; l'issue non indica file sorgente né test.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- arch-linux, cpp, typescript, vscode
- Ambito
- devtools, operating-systems
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100