Debug fail to start due GDB Server timeout

[J-Rios]

Hi,

I have started to work using a remote debugger (a JLink device connected in a remote machine and using the JLink Remote Server that creates a tunnel to Segger servers to allow remote connection to the debugger) and noticed that when you start the debug session via Cortex-Debug, it fails due GDB Server timeout.

I have tracked and found that the issue was caused due this fixed constant timeout to wait for GDB to start and be ready for the GDB client. That value is currently set to 10s, a valid value for USB, LAN and standard remote network connections, but seems sometimes could not be enough for some remote connections to external networks via VPN or tunnels.

Increasing this timeout for 20s (or maybe could be better 30s for extremely high latency connections) solves the issue (tested).

Here is a Pull Request proposal to fix this issue:
#1129

Best Regards :)

[J-Rios]

An extra idea could be to create some kind of new property (i.e. "gdbServerTimeoutMs") for launch.json configuration to allow the user setup this timeout value.

I didn't go that way cause it requires more changes in the code and I'm not fuent with typescript xD

[haneefdm]

Please try the latest pre-release. New timeout is 60 seconds...

https://github.com/Marus/cortex-debug/releases