Databases
StackOverflow2013
Postsdbo
PORemote GDB debugging
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORemote GDB debugging
    text
    copied!<p>I've just spent a whole day trying to find a way to enable GDB debugging from <a href="http://en.wikipedia.org/wiki/Qt_Creator" rel="nofollow noreferrer">Qt Creator</a> or Eclipse. I learned that there are basically two approaches to launch the target application:</p> <ul> <li>Using ssh (<code>ssh host gdb</code>)</li> <li>Using gdbserver</li> </ul> <p>I was able to use both approaches to launch gdb remotely and start the application. However, GDB never responds to any breakpoints set in the IDE. Also I can't pause the application to inspect the program state. In Qt Creator I just get an obscure stack trace (I might have been looking at the traces of ssh or gdb actually...).</p> <p>Can anyone help me to get started?</p> <h3>Progress!</h3> <p>I found that with Qt Creator 2.0 there is an feature called "Attach and debug remote application." It's based on gdbserver. The good thing is that it stops on the IDE's breakpoints. However, there are two issues:</p> <ul> <li>When it hits a breakpoint it only shows assembly code, not the source code.</li> <li>GDB often quits because of 'signal received'</li> </ul> <p>I should probably mention that the remote executable is compiled with an older version of GCC than the one installed on my local PC. Perhaps some of the problems are related to this.</p> <h3>Update</h3> <p>I should mention that I switched to running <a href="http://cgdb.sourceforge.net/" rel="nofollow noreferrer">cgdb</a> on the remote machine via SSH.</p> <p>The remote Qt Creator-based solution wasn't stable. GDB tends to quit because of mysterious 'signal received' messages.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload