microsoft / microsoft/vscode-cpptools
Unable to debug program that requires root permission in Linux VSCODE
@WardenGnaw ci sta già lavorando.
Dal 31/5/2020.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
Type: Debugger
I have seen previous workaround of using bash script to wrap gdb script. I have done that. But still I hit the following error showing in VScode Linux terminal
[1] + Stopped (tty output) "/usr/bin/gdb" --interpreter=mi --tty=${DbgTerm} 0<"/tmp/Microsoft-MIEngine-In-a950fu1m.9l8" 1>"/tmp/Microsoft-MIEngine-Out-gzjlvx7g.xil"
You have stopped jobs.
[sudo] password for kenneth:
sudo: unable to read password: Input/output error
My launch.json is as following
"version": "0.2.0",
"configurations": [
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "/home/kenneth/GitHub/rocksdb/examples/simple_example",
"args": [],
"stopAtEntry": true,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "/usr/bin/gdb",
"miDebuggerArgs": "-interpreter=mi --silent",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
]
}
Describe the bug
- OS and Version:Ubuntu
- VS Code Version: 1.45.0
- C/C++ Extension Version: 0.28.1
- Other extensions you installed (and if the issue persists after disabling them):
- A clear and concise description of what the bug is.
To Reproduce
Please include a code sample and launch.json configuration.
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Additional context
If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your launch.json
Add any other context about the problem here including log or error messages in your Debug Console or Output windows.
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.
Valutazione
Questa issue non è ancora stata valutata.