Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Deployment and Debugging
Forum Update on Monday, May 27th 2025

Deployment and Debugging

Scheduled Pinned Locked Moved Solved Mobile and Embedded
7 Posts 4 Posters 974 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SPlatten
    wrote on 24 May 2019, 12:25 last edited by
    #1

    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?

    Kind Regards,
    Sy

    R 1 Reply Last reply 24 May 2019, 23:15
    0
    • S SPlatten
      24 May 2019, 12:25

      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?

      R Offline
      R Offline
      raven-worx
      Moderators
      wrote on 24 May 2019, 23:15 last edited by raven-worx
      #2

      @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

      --- SUPPORT REQUESTS VIA CHAT WILL BE IGNORED ---
      If you have a question please use the forum so others can benefit from the solution in the future

      1 Reply Last reply
      2
      • S Offline
        S Offline
        SPlatten
        wrote on 27 May 2019, 14:09 last edited by
        #3

        @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.

        Kind Regards,
        Sy

        1 Reply Last reply
        0
        • D Offline
          D Offline
          Dr. Abel
          wrote on 28 May 2019, 00:24 last edited by
          #4

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

          S 1 Reply Last reply 28 May 2019, 20:22
          -1
          • S Offline
            S Offline
            SPlatten
            wrote on 28 May 2019, 06:53 last edited by
            #5

            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.

            Kind Regards,
            Sy

            1 Reply Last reply
            0
            • D Dr. Abel
              28 May 2019, 00:24

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

              S Offline
              S Offline
              SGaist
              Lifetime Qt Champion
              wrote on 28 May 2019, 20:22 last edited by
              #6

              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.

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              D 1 Reply Last reply 29 May 2019, 10:49
              2
              • S SGaist
                28 May 2019, 20:22

                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.

                D Offline
                D Offline
                Dr. Abel
                wrote on 29 May 2019, 10:49 last edited by
                #7

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

                1 Reply Last reply
                0

                1/7

                24 May 2019, 12:25

                • Login

                • Login or register to search.
                1 out of 7
                • First post
                  1/7
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved