Nicer workflow for GDB+attach

Type: Feature Request

I have a Python program that repeatedly compiles C++ code as a shared library, and launches it in a forked process.

The C++ code is run as soon as GDB is attached. I detect this by waiting for SIGUSR1.

In VSCode, I have to press F5, then F6, then Ctrl-Shift-Y, then type "-exec signal SIGUSR1". It would be nice if that sequence of actions could be automatically triggered via launch.json.

Unfortunately, "stopAtConnect" is not working, and neither is

"setupCommands": [
  {
      "text": "-interpreter-exec console \"signal SIGUSR1\"",
  }
]

Riprodurre la sequenza segnalata F5, F6 e Ctrl-Shift-Y con la configurazione GDB attach in launch.json, concentrandosi su stopAtConnect e setupCommands. Confrontare il comportamento configurato con l’esecuzione manuale di -exec signal SIGUSR1; done significa che la sequenza può essere attivata tramite launch.json e che il codice C++ viene avviato dopo l’attach.