microsoft / microsoft/vscode-cpptools
Debug Remote-Container GDB: Unable to open raise.c
@WardenGnaw arbeitet bereits daran.
Seit 23.4.2021.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 6.2k
- Forks
- 1.7k
- Ø Merge
- 14 Std. 46 Min.
- Gemergte PRs (30 T.)
- 61
Beschreibung
Bug type: Debugger
Describe the bug
- OS and Version: W10
- VS Code Version: 1.55.2
- C/C++ Extension Version: 1.3.1
- Other extensions you installed (and if the issue persists after disabling them): CMake
this is very similar to #1738
In my case it's in linked docker containers based on WSL2, so it makes sense I imagine.
The fix suggested there does not seem to work though.
the suggested fix:
"setupCommands": [
{
"description": "Skip <path> files",
"text": "-interpreter-exec console \"skip -gfi <path-to-ignore>/**/*\""
}
]
with path-to-ignore=path/to/glibc
in my case, the error is:
Unable to open 'raise.c': Unable to read file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6e696674795f6b65706c6572222c2273657474696e6773223a7b226365727450617468223a22433a5c5c55736572735c5c6b696c68655c5c2e646f636b65725c5c6d616368696e655c5c6365727473227d7d/build/glibc-eX1tMB/glibc-2.31/sysdeps/unix/sysv/linux/raise.c' (Error: Unable to resolve non-existing file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6e696674795f6b65706c6572222c2273657474696e6773223a7b226365727450617468223a22433a5c5c55736572735c5c6b696c68655c5c2e646f636b65725c5c6d616368696e655c5c6365727473227d7d/build/glibc-eX1tMB/glibc-2.31/sysdeps/unix/sysv/linux/raise.c').
I tried to add the rather long vscode-remote://[...]/build but it didn't change anything, the error pops and the file is still not found.
The files in the container are also available locally
How to remove this error or how to give access to these files?
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.