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. Unable to debug Android App (Windows + Qt Creator 12 + LLDB)

Unable to debug Android App (Windows + Qt Creator 12 + LLDB)

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
169 Posts 9 Posters 61.5k 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.
  • Ronel_qtmasterR Ronel_qtmaster

    @CodesInChaoss maybe you are using LLDB the wrong way with qt.
    Also, have you checked if it is the right version for your Qt version?
    How have you first of all added lldb in qt? which versiion of lldb are using?

    C Offline
    C Offline
    CodesInChaoss
    wrote on last edited by
    #14

    @Ronel_qtmaster

    Everything comes with defaults delivered by QT Creator 12, clean install of Windows.

    Ronel_qtmasterR 1 Reply Last reply
    0
    • C CodesInChaoss

      @Ronel_qtmaster

      Everything comes with defaults delivered by QT Creator 12, clean install of Windows.

      Ronel_qtmasterR Offline
      Ronel_qtmasterR Offline
      Ronel_qtmaster
      wrote on last edited by Ronel_qtmaster
      #15

      @CodesInChaoss LLDB is for linux, use GDB for windows
      check this https://doc.qt.io/qtcreator/creator-debugger-engines.html

      C 1 Reply Last reply
      0
      • Ronel_qtmasterR Ronel_qtmaster

        @CodesInChaoss LLDB is for linux, use GDB for windows
        check this https://doc.qt.io/qtcreator/creator-debugger-engines.html

        C Offline
        C Offline
        CodesInChaoss
        wrote on last edited by CodesInChaoss
        #16

        @Ronel_qtmaster

        yes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.

        I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.

        So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.

        lldb version 11.0.5
          clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
          llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
        
        C Ronel_qtmasterR 2 Replies Last reply
        0
        • C CodesInChaoss

          @Ronel_qtmaster

          yes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.

          I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.

          So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.

          lldb version 11.0.5
            clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
            llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
          
          C Offline
          C Offline
          CodesInChaoss
          wrote on last edited by CodesInChaoss
          #17

          As far as I know, LLDB never (before) came pre-installed on Windows installations alongside with QT Creator, I think.

          Now, on windows , all kits deployed by QT Creator , by default have this:
          ecb2f846-1708-4710-8a2f-1dc06e508e5b-image.png

          1 Reply Last reply
          0
          • C CodesInChaoss

            @Ronel_qtmaster

            yes I've seen this page already BUT it seems that recent versions of QT Creator enforce use of LLDB (also by default) on WIndows. There are tickets in Bug-Reports saying that they've 'transitioned'.

            I've always worked with GDB on WIndows with QT Creator, but to all my surprise, after installation of QT Creator 12 (we've transitioned to Commercial License) LLDB was selected and enabled BY DEFAULT on all kits.

            So I said to myself, ok - let's go. I knew LLDB was for mac since that's what we've been using for iOS deployment.

            lldb version 11.0.5
              clang revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
              llvm revision 87f1315dfbea7c137aa2e6d362dbb457e388158d
            
            Ronel_qtmasterR Offline
            Ronel_qtmasterR Offline
            Ronel_qtmaster
            wrote on last edited by
            #18

            @CodesInChaoss Do you mean that you have installed lldb with the online installler?

            C 1 Reply Last reply
            0
            • Ronel_qtmasterR Ronel_qtmaster

              @CodesInChaoss Do you mean that you have installed lldb with the online installler?

              C Offline
              C Offline
              CodesInChaoss
              wrote on last edited by CodesInChaoss
              #19

              @Ronel_qtmaster
              Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16

              Ronel_qtmasterR C 2 Replies Last reply
              0
              • C CodesInChaoss

                @Ronel_qtmaster
                Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16

                Ronel_qtmasterR Offline
                Ronel_qtmasterR Offline
                Ronel_qtmaster
                wrote on last edited by
                #20
                This post is deleted!
                1 Reply Last reply
                0
                • C CodesInChaoss

                  @Ronel_qtmaster
                  Well it must have arrived with the online installer, yes, by default since I've used all the default tickers which go for Qt 5.15.16

                  C Offline
                  C Offline
                  CodesInChaoss
                  wrote on last edited by CodesInChaoss
                  #21

                  When I choose GDB rebuild the app none of the breakpoints are ever hit GDB reports version 8.3 ( installed by Qt I presume).

                  6ddd997d-7e76-4029-a441-872492d08a6c-image.png

                  4488c593-03bb-44c7-bc95-e18046df6536-image.png

                  6b4280e3-4837-46c4-9691-e81270a7938d-image.png

                  The effect with GDB is that the app waits for debugger, the app runs (the breakpoints I set are not hit - in main())

                  yes yes, it works I'm not a noob, the app has been tested by thousands already.

                  C 1 Reply Last reply
                  0
                  • C CodesInChaoss

                    When I choose GDB rebuild the app none of the breakpoints are ever hit GDB reports version 8.3 ( installed by Qt I presume).

                    6ddd997d-7e76-4029-a441-872492d08a6c-image.png

                    4488c593-03bb-44c7-bc95-e18046df6536-image.png

                    6b4280e3-4837-46c4-9691-e81270a7938d-image.png

                    The effect with GDB is that the app waits for debugger, the app runs (the breakpoints I set are not hit - in main())

                    yes yes, it works I'm not a noob, the app has been tested by thousands already.

                    C Offline
                    C Offline
                    CodesInChaoss
                    wrote on last edited by
                    #22

                    It's like I've had everything set up and running perfect but something made me update from QT Creator 10 (community edition) towards QT Creator 12 and here I am.

                    C 1 Reply Last reply
                    0
                    • C CodesInChaoss

                      It's like I've had everything set up and running perfect but something made me update from QT Creator 10 (community edition) towards QT Creator 12 and here I am.

                      C Offline
                      C Offline
                      CodesInChaoss
                      wrote on last edited by
                      #23

                      seems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).

                      These things do not come as part of the Online Installer.

                      C Ronel_qtmasterR 2 Replies Last reply
                      0
                      • C CodesInChaoss

                        seems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).

                        These things do not come as part of the Online Installer.

                        C Offline
                        C Offline
                        CodesInChaoss
                        wrote on last edited by CodesInChaoss
                        #24

                        Can anyone else confirm that we are STILL to be using GDB on Windows with QT creator when debugging Android apps, please?

                        I'm more than fine with just about anything that works.

                        1 Reply Last reply
                        0
                        • C CodesInChaoss

                          seems as both LLDB and GDB come as part of Android SDK/NDK so these have been installed by QT Creator itself during Android bootstrapping (autonomous).

                          These things do not come as part of the Online Installer.

                          Ronel_qtmasterR Offline
                          Ronel_qtmasterR Offline
                          Ronel_qtmaster
                          wrote on last edited by
                          #25

                          @CodesInChaoss Qt does not install android sdk and ndk during update.You have to do that externelly so if you have updated Qt it might be possible that your ndk version is conflicting somewhere

                          C 1 Reply Last reply
                          0
                          • Ronel_qtmasterR Ronel_qtmaster

                            @CodesInChaoss Qt does not install android sdk and ndk during update.You have to do that externelly so if you have updated Qt it might be possible that your ndk version is conflicting somewhere

                            C Offline
                            C Offline
                            CodesInChaoss
                            wrote on last edited by
                            #26

                            @Ronel_qtmaster

                            my friend, 6e6b53f7-567a-477f-ac4d-94bdb35bca74-image.png

                            Above, for a couple of YEARS now.

                            And I've been using QT when nothing fancy like that was around trust me when I say.

                            C 1 Reply Last reply
                            0
                            • C CodesInChaoss

                              @Ronel_qtmaster

                              my friend, 6e6b53f7-567a-477f-ac4d-94bdb35bca74-image.png

                              Above, for a couple of YEARS now.

                              And I've been using QT when nothing fancy like that was around trust me when I say.

                              C Offline
                              C Offline
                              CodesInChaoss
                              wrote on last edited by CodesInChaoss
                              #27

                              I've been seeing lots and lots of deep sh** when it comes to QT... I've been deep down. Trust me when I say, it's all doomed but I love it but only because I'm a low-level type of a guy.. I can't possibly IMAGINE any typical developer using it. I simply cannot. Not for mobile. And not from WIndows.

                              Ronel_qtmasterR 1 Reply Last reply
                              0
                              • C CodesInChaoss

                                I've been seeing lots and lots of deep sh** when it comes to QT... I've been deep down. Trust me when I say, it's all doomed but I love it but only because I'm a low-level type of a guy.. I can't possibly IMAGINE any typical developer using it. I simply cannot. Not for mobile. And not from WIndows.

                                Ronel_qtmasterR Offline
                                Ronel_qtmasterR Offline
                                Ronel_qtmaster
                                wrote on last edited by
                                #28
                                This post is deleted!
                                C 1 Reply Last reply
                                0
                                • Ronel_qtmasterR Ronel_qtmaster

                                  This post is deleted!

                                  C Offline
                                  C Offline
                                  CodesInChaoss
                                  wrote on last edited by CodesInChaoss
                                  #29

                                  @Ronel_qtmaster

                                  Dear Ronel I'll tell you that I've even got GDB 'working' for me but it took quite a few ADB commands and manual creation of folders on my Android device, now tell, me is this a unified QT Multi-Platform Development framework?

                                  How a typical developer is supposed to get around these issues?

                                  Why LLDB set by default?

                                  Now I know it's not QT support.

                                  Anyway I'm still looking into making the android app actually not skip the initial breakpoints.

                                  C 1 Reply Last reply
                                  0
                                  • C CodesInChaoss

                                    @Ronel_qtmaster

                                    Dear Ronel I'll tell you that I've even got GDB 'working' for me but it took quite a few ADB commands and manual creation of folders on my Android device, now tell, me is this a unified QT Multi-Platform Development framework?

                                    How a typical developer is supposed to get around these issues?

                                    Why LLDB set by default?

                                    Now I know it's not QT support.

                                    Anyway I'm still looking into making the android app actually not skip the initial breakpoints.

                                    C Offline
                                    C Offline
                                    CodesInChaoss
                                    wrote on last edited by
                                    #30

                                    When running the app under GDB (Xiaomi device) I'm getting SigSegvs in a thread named "ScoutStat" asm code.

                                    Anyone knows what this might be? It's not part of my app, the app runs fine.

                                    C 1 Reply Last reply
                                    0
                                    • C CodesInChaoss

                                      When running the app under GDB (Xiaomi device) I'm getting SigSegvs in a thread named "ScoutStat" asm code.

                                      Anyone knows what this might be? It's not part of my app, the app runs fine.

                                      C Offline
                                      C Offline
                                      CodesInChaoss
                                      wrote on last edited by CodesInChaoss
                                      #31

                                      So yeah.. so it seems that the signals received previously by LLDB (but QT was not showing ANY dialog-boxes) or the actual Signal Code, are in fact segmentation faults coming from something name 'Scout Stat' Anyone knows what this is?

                                      C 1 Reply Last reply
                                      0
                                      • C CodesInChaoss

                                        So yeah.. so it seems that the signals received previously by LLDB (but QT was not showing ANY dialog-boxes) or the actual Signal Code, are in fact segmentation faults coming from something name 'Scout Stat' Anyone knows what this is?

                                        C Offline
                                        C Offline
                                        CodesInChaoss
                                        wrote on last edited by
                                        #32

                                        9860c293-1da2-4733-a27d-4688c0ca7a36-image.png @CodesInChaoss

                                        That's not part of my code and something presumably operating as part of QT ?

                                        C 1 Reply Last reply
                                        0
                                        • C CodesInChaoss

                                          9860c293-1da2-4733-a27d-4688c0ca7a36-image.png @CodesInChaoss

                                          That's not part of my code and something presumably operating as part of QT ?

                                          C Offline
                                          C Offline
                                          CodesInChaoss
                                          wrote on last edited by CodesInChaoss
                                          #33

                                          Ok folks so there's that MAGICAL
                                          'scoutstat' thread, I have no idea what it is that is causing havoc.

                                          It must be something related to UI/rendering/UI interactions since the segmentation fault would be signaled only as a result of UI interactions/ UI animations/ preparations.

                                          What's that and why the heck it's sig-faulting on meh

                                          Not my code. And presumably not part of source code that arrive with QT pre-installed since QT does not bring me to these.

                                          C 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