Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
how to configure project for debugging when cross compiling
Waldi79 last edited by
I am developing on an ubuntu box an application for a arm v7 based embedded board.
I am facing problems when debuging the cross compiled arm project. When the debugger starts, I get the following suspicious output:
Debugging starts Listening on port 10001 Remote debugging from host 10.1.0.3 while parsing target description (at line 1): Target description specified unknown architecture "arm" Could not load XML target description; ignoring Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code
then the application starts and all qDebug() output is displayed in the
application output pane.
When the app reaches the first breakpoint, the following error message appears:
The inferior stopped because it received a signal from the operating system.
Signal name: SIGSEGV
Signal meaning: Segmentation fault
The embedded board has no gdbserver preinstalled, so I downloaded the source and cross
compiled it. As far as I see, there is no malfunction whatssoever with gdbserver.
Further, I missing the basic understanding how cross debugging works. How does gdb handle the different
executable types. gdbserver in my understanding is only a hose for gdb information to and from the target.
Is there a better documentation available?
skypuppy last edited by
Bear in mind that I have NO idea what I'm talking about. However, if using QtCreator, have you set up your "kit" under tools on the big computer (not the embedded one?) :)
Which platform are you using? I'm trying to get RPi2 and Beaglebone Black (BBBj) to cooperate with Qt Creator on Debian Wheezy Linux PC, and so far, not working at all. So take my suggestion with a grain of salt.
Also, you can run the full Qt on the arm (without using a host PC) with lots and lots and lots of patience and diligence. I got it to work on an RPi2 (mostly) but not yet on a BBB.