Deployment and Debugging

SPlatten

I'm using Qt Creator 3.5.1 based on Qt 5.5.1 (GCC 5.2.1 20151129, 32 bit) running on Ubuntu 16.04.

I have a device set-up and using the Test button it connects to the host, checks the kernel version (Linux 2.6.37 armv7l) and the result is Device test finished successfully.

The project builds find with no errors, I then deploy to the device, no errors, green bar all the way to the end.

Now I try to debug the application, in the Application Output:

    Debugging starts
    Listening on port 10000
    Remote debugging from host 192.168.1.199
    Process /data/user/appname created: pid = 3366
    Unable to find dynamic linker breakpoint function.
    GDB will be unable to debug shared library initialisers
    and track explicitly loaded dynamic code.Could not load shared library symbols for 21 libraries, e.g. /usr/lib/libacs_api.so.
    Use the "info shared library" command to see the complete listing.
    Do you need "set solid-search-path" or "set sys root"?QWSocket::connectToLocalFile could not connect:: Connection refused
    QWSocket::connectToLocalFile could not connect:: Connection refused
    QWSocket::connectToLocalFile could not connect:: Connection refused
    QWSocket::connectToLocalFile could not connect:: Connection refused
    QWSocket::connectToLocalFile could not connect:: Connection refused
    QWSocket::connectToLocalFile could not connect:: Connection refused
    No Qt for Embedded Linux server appears to be running.
    If you want to run this program as a server,
    add the "-qws" command-line option.
    
    Child exited with status 1
    Debugging has finished

I have managed to debug on this target before and I have no idea why it isn't working now...any suggestions?

raven-worx

@SPlatten
did you try to run your program with -qws argument as suggested by the log you've posted?
I assume you are using Qt4? If so you should read this

SPlatten

@raven-worx said in Deployment and Debugging:

this

Thank you so much, adding -qws worked a treat...I really must read what is put in front of me.

Dr. Abel

Your building is on Qt 5.5.1 sdk,
but your device is configured in Qt 4 sdk.
Mybe this caused.

SPlatten

I have no choice as the SDK is supplied by ACR and that version is as up to date as is available for the target device.

SGaist

Hi,

@Dr.-Abel said in Deployment and Debugging:

Your building is on Qt 5.5.1 sdk,
but your device is configured in Qt 4 sdk.
Mybe this caused.

That's the version of Qt used to build Qt Creator. It's unrelated to the version of Qt you are using to build your application.

Dr. Abel

@SGaist Yeah, he may be building app in Qt5, but using on device with Qt4.