microsoft / microsoft/vscode-cpptools

Debug Remote-Container GDB: Unable to open raise.c

Abierto
#7,401 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@WardenGnaw ya está trabajando en esto.

Desde el 23/4/2021.

debugger
Lenguaje dominante
TypeScript
Estrellas
6.2k
Forks
1.7k
Merge medio
14 h 46 min
PR fusionados (30 d)
61

Descripción

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?

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.