>> when we all rode horses to work
Funny! Before the industrial revolution but after dinasours and the wheelI see your point that if it runs in VSC it can probably run in SE.
I ignored the warning about the GDB version as you suggested. I setup the File, Socket Addr & Port, & GDB Configuration. Also, I set the timeout to the max of 10 seconds.
I get the error: "Error starting debugger: GDB has terminated prematurely"
When I check the remote unit via telnet, it is still listening and waiting.
Just for grins, I tried to connect via Debug->Attach Debugger->Attach to Remote Process (LLDB). This brings up a debug session in SE. Also, in telnet, the remote device shows "Remote debugging from host 192.168.169.2". However, nothing in the SE debug session is working and it exits after 20 seconds or so.
I don't think that it is supposed to work with LLDB, but I tried it on a whim and thought it might offer a clue.
Lastly, I captured this from the DEBUG CONSOLE in VSCode:
GNU gdb (GDB) 7.1
Copyright (C) 2010 Free Software Foundation, Inc.
So, even though my compiler is 4.4.4, it seems the GDB is 7.1. New to Linux, so I don't know if 7.1 is the GDB executable running on Ubuntu, the GDB Server running on the embedded device, or both.
hs2:
Thanks for the suggestion. I will try that after giving up on the current GDB. Not there yet, but I can see it on the horizon.