[Solved] Qt5 Debugging Problem
-
Hi,
I have Qt5 running on the Beaglebone Black
I can build an application, deploy and run the application fine.
The problem is I am unable to debug the application within Qt Creator.
I can debug the application from the command line.
When I try to debug with Qt Creator I get the following on the application output tab...
Debugging starts
Listening on port 2001
Debugging has failed
Debugging has finishedThe log output is:
QProcess: Destroyed while process ("/opt/poky/qt5/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb") is still running.
Warning: User requested stop. Shutting down...
(no active run control)
Warning: HANDLE RUNCONTROL START FAILED (no active run control)
Warning: State changed from EngineSetupFailed(2) to DebuggerFinished(23) [master] (no active run control)
Warning: State changed from EngineSetupFailed(2) to DebuggerFinished(23) (no active run control)
Warning: (gdb) (no active run control)
Warning: QUIT DEBUGGER REQUESTED IN STATE 23 (no active run control)
Warning: 107^done (no active run control)
Warning: (gdb) (no active run control)
Warning: =cmd-param-changed,param="detach-on-fork",value="off" (no active run control)
Warning: 108^done (no active run control)
Warning: (gdb) (no active run control)I have tested the device connection and it passes.
Connecting to host...
Checking kernel version...
Linux 3.14.0-yocto-standard armv7lChecking if specified ports are available...
All specified ports are available.Device test finished successfully.
Other Info
Running Qt Creator on Ubuntu 14.04LTSI built the images with Yocto adding Qt5.21 from https://github.com/meta-qt5/meta-qt5.git
Qt Creator 3.4.0Any help or hints would be very much appreciated
Thanks,
Louis -
-
@LouisRyan
Hi and welcome to devnetHow to mark as solved?
Simply go to the first post where you started. Press the gear wheel on the very right and select the left (Edit) symbol.
Go to your title and add there [solved] in the beginning of line.I will mark it as solved this time for you.
-
@LouisRyan Thanks...