Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Cannot run the Simple MQTT Client Example on Raspberry Pi
Forum Updated to NodeBB v4.3 + New Features

Cannot run the Simple MQTT Client Example on Raspberry Pi

Scheduled Pinned Locked Moved Unsolved General and Desktop
5 Posts 2 Posters 448 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.
  • I Offline
    I Offline
    isan
    wrote on 4 Aug 2020, 08:14 last edited by
    #1

    I compiled QT 5.11 for Raspberry pi and built the qtmqtt module for it. But when I run simple MQTT client example I get this error on the raspberry: the process killed by the signal and the program closes, what is the reason?do I should other setting for mqtt in raspberry?

    J 1 Reply Last reply 4 Aug 2020, 08:15
    0
    • I isan
      4 Aug 2020, 08:14

      I compiled QT 5.11 for Raspberry pi and built the qtmqtt module for it. But when I run simple MQTT client example I get this error on the raspberry: the process killed by the signal and the program closes, what is the reason?do I should other setting for mqtt in raspberry?

      J Offline
      J Offline
      jsulm
      Lifetime Qt Champion
      wrote on 4 Aug 2020, 08:15 last edited by
      #2

      @isan said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

      what is the reason?

      Please use debugger to get stack trace

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      I 1 Reply Last reply 5 Aug 2020, 07:45
      0
      • J jsulm
        4 Aug 2020, 08:15

        @isan said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

        what is the reason?

        Please use debugger to get stack trace

        I Offline
        I Offline
        isan
        wrote on 5 Aug 2020, 07:45 last edited by isan 8 May 2020, 07:46
        #3

        @jsulm when I use debugger I get the error : The selected build of GDB does not support Python scripting.

        I installed gdb-multiarch on my development host (Ubuntu):

        sudo apt-get install gdb-multiarch

        Then in the Debuggers tab of QtCreator I added a new manual entry:
        Name: Multiarch GDB
        Path: /usr/bin/gdb-multiarch

        And in the Raspberry Pi Kit tab of QtCreator I selected Multiarch GDB as your Debugger.

        Then when I use debugger I get

        Process /home/pi/simplemqttclient created; pid = 15405
        Could not load shared library symbols for 5 libraries, e.g. /usr/local/qt5pi/lib/libQt5Widgets.so.5.
        Use the "info sharedlibrary" command to see the complete listing.
        Do you need "set solib-search-path" or "set sysroot"?
        
        Child terminated with signal = 0x4 (SIGILL)
        

        I have libQt5Widgets.so.5.library in /usr/local/qt5pi/lib address
        And I added

        handle SIGILL pass nostop noprint
        info sharedlibrary
        set solib-search-path ./Debug/
        

        In additional startup commands GDB debugger tap window
        But the problem is still exist!

        J 1 Reply Last reply 5 Aug 2020, 08:12
        0
        • I isan
          5 Aug 2020, 07:45

          @jsulm when I use debugger I get the error : The selected build of GDB does not support Python scripting.

          I installed gdb-multiarch on my development host (Ubuntu):

          sudo apt-get install gdb-multiarch

          Then in the Debuggers tab of QtCreator I added a new manual entry:
          Name: Multiarch GDB
          Path: /usr/bin/gdb-multiarch

          And in the Raspberry Pi Kit tab of QtCreator I selected Multiarch GDB as your Debugger.

          Then when I use debugger I get

          Process /home/pi/simplemqttclient created; pid = 15405
          Could not load shared library symbols for 5 libraries, e.g. /usr/local/qt5pi/lib/libQt5Widgets.so.5.
          Use the "info sharedlibrary" command to see the complete listing.
          Do you need "set solib-search-path" or "set sysroot"?
          
          Child terminated with signal = 0x4 (SIGILL)
          

          I have libQt5Widgets.so.5.library in /usr/local/qt5pi/lib address
          And I added

          handle SIGILL pass nostop noprint
          info sharedlibrary
          set solib-search-path ./Debug/
          

          In additional startup commands GDB debugger tap window
          But the problem is still exist!

          J Offline
          J Offline
          jsulm
          Lifetime Qt Champion
          wrote on 5 Aug 2020, 08:12 last edited by
          #4

          @isan said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

          set solib-search-path ./Debug/

          Since your Qt libs are in /usr/local/qt5pi/lib it should be

          set solib-search-path /usr/local/qt5pi/lib
          

          I would say.

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          I 1 Reply Last reply 15 Aug 2020, 15:24
          0
          • J jsulm
            5 Aug 2020, 08:12

            @isan said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

            set solib-search-path ./Debug/

            Since your Qt libs are in /usr/local/qt5pi/lib it should be

            set solib-search-path /usr/local/qt5pi/lib
            

            I would say.

            I Offline
            I Offline
            isan
            wrote on 15 Aug 2020, 15:24 last edited by isan
            #5

            @jsulm said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

            @isan said in Cannot run the Simple MQTT Client Example on Raspberry Pi:

            set solib-search-path ./Debug/

            Since your Qt libs are in /usr/local/qt5pi/lib it should be

            set solib-search-path /usr/local/qt5pi/lib
            

            I would say.

            I did it,
            And I also did this on RPI:

            echo /usr/local/qt5pi/lib | sudo tee /etc/ld.so.conf.d/qt5pi.conf
            sudo ldconfig
            

            But the problem still exists.

            1 Reply Last reply
            0

            • Login

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