#638 debuggergdb: add pipe remote debugging protocol

[Thomas Sailer]

The C::B debuggergdb plugin already supports remote debugging with gdb (target {,extended-}remote command) using various transports (currently TCP, UDP and serial).

This patch adds support for a fourth method, namely pipes. In this mode, gdb takes care of running and shutting down the debug server, and the user need not take care of ports or serial interfaces.

Typically, it is used like this:
target extended-remote | openocd ...
for developing embedded software running on external hardware, where openocd acts as the link between the host computer/gdb and the target CPU.

[Teodor Petrov]

Can you try this a bit modified patch?

[Teodor Petrov]

Any feedback on the patch, because I want to push it to trunk?

[bluehazzard]

i tried to test it on windows and it seems to work (at the moment i have no hardware to test it properly). Paths have to be escaped with \ but i don't think this is something codeblocks should solve...
The thing that bothers me a bit is that the controls in the settings dialog are always active. If i select serial port it should deactivate the other text fields (ip address, port, pipe) ecc. Not clear it, only deactivating...