|Two attempts to start gdbserver for C/C++ remote debug? [message #1751751]
||Fri, 13 January 2017 13:30
| Adrian Oltean
Registered: December 2016
While trying to figure out why am I seeing the problem described in https://www.eclipse.org/forums/index.php/t/1083109/ I tried the same remote debugging scenario on my Ubuntu 14.04 64-bit. So what I'm doing is the following:
1. Install Eclipse Neon.2 IDE for C/C++ developer
2. Start eclipse
3. Create a hello world C project
4. Build project
5. Create a new C/C++ Remote Application debug configuration
6. Create a new SSH connection and use 127.0.0.1 as remote host
7. Configure the other things required (e.g. remote file path)
Looking in the Remote Shell Console I see a difference compared to what I see when I'm using an ARMv8 target. I see that command "gdbserver :2345 /tmp/threads;exit" is executed twice when connecting to 127.0.0.1 and only once when I'm using the cross-compiled GDB and my ARMv8 target. Where does this difference come from? By retrying execution of "gdbserver :2345 /tmp/threads;exit" I can debug the app on my Linux host but can't say the same when trying on my ARMv8 target.
Console output when connecting to 127.0.0.1 is the following:
Last login: Fri Jan 13 15:06:54 2017 from localhost
gdbserver :2345 /tmp/threads;exit
[4mfsr-ub1464-107[m:[1m~[0m> gdbserver :2345 /tmp/threads;exit
Process /tmp/threads created; pid = 23558
Listening on port 2345
Remote debugging from host 127.0.0.1
You can also notice some strange characters printed "[4mfsr-ub1464-107[m:[1m~[0m".
Can someone explain why is the command executed twice on one setup and only once on the other?
Powered by FUDForum
. Page generated in 0.02176 seconds