Start GDB as a separate process (signing problem)

See

• https://github.com/Microsoft/vscode-cpptools/issues/763#issuecomment-326626829
• https://github.com/Microsoft/vscode-cpptools/issues/815#issuecomment-342568664

There is a huge problem with this extension that we can't use it with custom toolchain (especially for embedded) which is not signed (macOS). I understand that developers of this extension force people to switch to Windows. However, users should have a choice between OS.

The problem is linked with a bad architecture of this extension. Instead of a correct spawning of GDB via a separate process with a VALID current working directory per process (see #815), someone invented "bicycle" and places GDB into an external script which spawns it later. I don't have comments for that...

MacOS DOES NOT allow spawning of AppleScript/Internal programs which are not signed. What should we (embedded developers) do with a dozen of toolchains for different architectures which are not signed?

Currently, the good alternative is https://marketplace.visualstudio.com/items?itemName=webfreak.debug. It has CORRECT behavior, the same which have other popular professional IDEs (Eclipse, etc). However, @WebFreak001 does not have time to maintain it. There are a few issues with a new VSCode related to breakpoints, etc.

This extension works only with an OFFICIAL toolchain for desktop development under macOS.

/cc @robotdad @pieandcakes

Inizia esaminando le issue e i commenti collegati, quindi traccia il modo in cui l’estensione avvia attualmente GDB su macOS. Il lavoro è completato quando le toolchain personalizzate non firmate possono essere avviate come processi separati senza dipendere da AppleScript o attivare il problema di firma descritto qui.