I'm trying to do some remote debugging and working from one machine to another in the same city works fine. However, I have a case where I want to remotely debug something on another continent and then I get a message like this:
Command timed out
I think that often happened in the past for many reasons but not much lately. This time I think it actually is a timeout. I have this in my .gdbinit file:
set tcp connect-timeout 300
Running with command line gdb verifies that it then tries to connect for 5 minutes, but CLion is too impatient for that. 5 minutes is of course overkill, but I was using that to test.
Is the Command timed out that I see a message from CLion or is it a gdb message and for some reason gdb inside CLion runs differently?
Is there a way to fix this?