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.4k 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.
  • C CodesInChaoss
    20 Feb 2024, 11:59

    otherwise it would just remain stuck at ```
    D libGRIDNEToken_arm64-v8a.so: QML Debugger: Waiting for connection on port 51672...

    forever
    C Offline
    C Offline
    CodesInChaoss
    wrote on 20 Feb 2024, 12:06 last edited by CodesInChaoss
    #43

    I'm also getting segmentation faults in 'binder:X' threads on UI interactions.

    Yet again, if I ignore these the app runs FINE.

    ideas?

    It's like tapping on an UI element is almost guaranteed to result in such a SigFault.

    C 1 Reply Last reply 20 Feb 2024, 12:12
    0
    • C CodesInChaoss
      20 Feb 2024, 12:06

      I'm also getting segmentation faults in 'binder:X' threads on UI interactions.

      Yet again, if I ignore these the app runs FINE.

      ideas?

      It's like tapping on an UI element is almost guaranteed to result in such a SigFault.

      C Offline
      C Offline
      CodesInChaoss
      wrote on 20 Feb 2024, 12:12 last edited by CodesInChaoss
      #44

      @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

      I'm also getting segmentation faults in 'binder:X' threads on UI interactions.

      Yet again, if I ignore these the app runs FINE.

      ideas?

      It's like tapping on an UI element is almost guaranteed to result in such a SigFault.

      The moment one pastes anything to 9e826d33-8519-41d4-98b8-7c24c76f2c26-image.png

      QT Creator crashed, Lo and Behold

      On my way to reconfigure everything anew.

      this feels like an early Alpha of some wanna-be development framework not something that has been around for many many years.

      Something I paid for.

      R J 2 Replies Last reply 20 Feb 2024, 12:15
      0
      • C CodesInChaoss
        20 Feb 2024, 12:12

        @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

        I'm also getting segmentation faults in 'binder:X' threads on UI interactions.

        Yet again, if I ignore these the app runs FINE.

        ideas?

        It's like tapping on an UI element is almost guaranteed to result in such a SigFault.

        The moment one pastes anything to 9e826d33-8519-41d4-98b8-7c24c76f2c26-image.png

        QT Creator crashed, Lo and Behold

        On my way to reconfigure everything anew.

        this feels like an early Alpha of some wanna-be development framework not something that has been around for many many years.

        Something I paid for.

        R Online
        R Online
        Ronel_qtmaster
        wrote on 20 Feb 2024, 12:15 last edited by
        #45

        @CodesInChaoss I am pretty sure that it is mostly related to the update process

        C 1 Reply Last reply 20 Feb 2024, 12:19
        0
        • R Ronel_qtmaster
          20 Feb 2024, 12:15

          @CodesInChaoss I am pretty sure that it is mostly related to the update process

          C Offline
          C Offline
          CodesInChaoss
          wrote on 20 Feb 2024, 12:19 last edited by CodesInChaoss
          #46

          @Ronel_qtmaster

          yeah sure but for the fact I've wiped out everything QT related.

          • QT has been wiped CLEAN the entire QT folder
          • everything in AppData QT related WIPED clean as well.
          • NDK/ SDK everything installed anew
          • same stuff on a fresh VM (like I've explaiend)
          1 Reply Last reply
          0
          • C CodesInChaoss
            20 Feb 2024, 12:12

            @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

            I'm also getting segmentation faults in 'binder:X' threads on UI interactions.

            Yet again, if I ignore these the app runs FINE.

            ideas?

            It's like tapping on an UI element is almost guaranteed to result in such a SigFault.

            The moment one pastes anything to 9e826d33-8519-41d4-98b8-7c24c76f2c26-image.png

            QT Creator crashed, Lo and Behold

            On my way to reconfigure everything anew.

            this feels like an early Alpha of some wanna-be development framework not something that has been around for many many years.

            Something I paid for.

            J Offline
            J Offline
            JonB
            wrote on 20 Feb 2024, 12:24 last edited by JonB
            #47

            @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

            Something I paid for.

            If you mean you have purchased a commercial licence from TQtC you can raise your issues with them for their attention.

            If you are using the free, open source version then that is not available and here we are just other users of Qt like yourself.

            C 1 Reply Last reply 20 Feb 2024, 12:28
            0
            • J JonB
              20 Feb 2024, 12:24

              @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

              Something I paid for.

              If you mean you have purchased a commercial licence from TQtC you can raise your issues with them for their attention.

              If you are using the free, open source version then that is not available and here we are just other users of Qt like yourself.

              C Offline
              C Offline
              CodesInChaoss
              wrote on 20 Feb 2024, 12:28 last edited by CodesInChaoss
              #48

              @JonB

              We've bought the 'cheap' startup license or I recall 600USD per year per person.

              Now, it does not come with technical support (as it tuned out).

              As we've learned the hard way that is.

              Now, I've forced GDB manually to neglect any segmentation faults (!!!) and Sig33s (..) by typing the custom arguments to QT Creator by hand as copy-pasting would result it to CRASH.

              Now I'm able to debug.. I'm not disturbed by QT's internal segmentation faults... I presume? correct me if I'm wrong

              C J E 3 Replies Last reply 20 Feb 2024, 12:34
              0
              • C CodesInChaoss
                20 Feb 2024, 12:28

                @JonB

                We've bought the 'cheap' startup license or I recall 600USD per year per person.

                Now, it does not come with technical support (as it tuned out).

                As we've learned the hard way that is.

                Now, I've forced GDB manually to neglect any segmentation faults (!!!) and Sig33s (..) by typing the custom arguments to QT Creator by hand as copy-pasting would result it to CRASH.

                Now I'm able to debug.. I'm not disturbed by QT's internal segmentation faults... I presume? correct me if I'm wrong

                C Offline
                C Offline
                CodesInChaoss
                wrote on 20 Feb 2024, 12:34 last edited by
                #49

                3059620d-fd45-43b9-b28b-145241b9bf98-image.png

                Something I haven't seen for like 4 years

                1 Reply Last reply
                0
                • C CodesInChaoss
                  20 Feb 2024, 12:28

                  @JonB

                  We've bought the 'cheap' startup license or I recall 600USD per year per person.

                  Now, it does not come with technical support (as it tuned out).

                  As we've learned the hard way that is.

                  Now, I've forced GDB manually to neglect any segmentation faults (!!!) and Sig33s (..) by typing the custom arguments to QT Creator by hand as copy-pasting would result it to CRASH.

                  Now I'm able to debug.. I'm not disturbed by QT's internal segmentation faults... I presume? correct me if I'm wrong

                  J Offline
                  J Offline
                  JonB
                  wrote on 20 Feb 2024, 12:38 last edited by
                  #50

                  @CodesInChaoss
                  Ah, I did not know about that licence's terms.

                  I'm not sure whether in "QT's internal segmentation faults" you mean Qt itself or Qt Creator. I would be worried about either, certainly if Qt code itself in your application is faulting, but I don't know what "workarounds" you need/have to live with for your situation.

                  Be aware that even without paid support you can raise bugs, against either Qt or Creator, at https://bugreports.qt.io/. People there look at them and respond/fix, regardless of OP's license state. I think Creator is regularly undergoing new releases, I don't know how robust it is for Android stuff.

                  C 1 Reply Last reply 20 Feb 2024, 12:41
                  0
                  • J JonB
                    20 Feb 2024, 12:38

                    @CodesInChaoss
                    Ah, I did not know about that licence's terms.

                    I'm not sure whether in "QT's internal segmentation faults" you mean Qt itself or Qt Creator. I would be worried about either, certainly if Qt code itself in your application is faulting, but I don't know what "workarounds" you need/have to live with for your situation.

                    Be aware that even without paid support you can raise bugs, against either Qt or Creator, at https://bugreports.qt.io/. People there look at them and respond/fix, regardless of OP's license state. I think Creator is regularly undergoing new releases, I don't know how robust it is for Android stuff.

                    C Offline
                    C Offline
                    CodesInChaoss
                    wrote on 20 Feb 2024, 12:41 last edited by
                    #51

                    @JonB

                    yes yes yes dear friend I know... I've been raising bugs from a different account for years ... we've all been developing QT since then kicked us in the ass years ago and run away with source code.

                    I know I can.

                    Then I get to wait 1-2 years till fix-ups make their way into commercial license and another 2 years into open source.

                    I know.

                    C 1 Reply Last reply 20 Feb 2024, 13:25
                    0
                    • C CodesInChaoss
                      20 Feb 2024, 12:41

                      @JonB

                      yes yes yes dear friend I know... I've been raising bugs from a different account for years ... we've all been developing QT since then kicked us in the ass years ago and run away with source code.

                      I know I can.

                      Then I get to wait 1-2 years till fix-ups make their way into commercial license and another 2 years into open source.

                      I know.

                      C Offline
                      C Offline
                      CodesInChaoss
                      wrote on 20 Feb 2024, 13:25 last edited by
                      #52

                      As of now

                      • we are manually overriding QT's Segmentation Fault events
                      • overriding Sig33 signals (bionic hardware)

                      Under the above conditions we are able to debug through QT Creator 12 and GDB with Qt 5.15.16 BUT

                      • removal of any breakpoint causes the GDB connection to become corrupted.
                      • no further debugging would be possible

                      Anyway, we CAN live with that (hopefully).

                      The most pressing issue is - how to force the mobile app to actually wait for QT Creator to fully attach?

                      I don't know the details but it seems that QT Creator 12 attached through GDB, the app knows.. BUT... NO BREAKPOINTS WOULD FIRE FOR 2-3 minutes at all (creator would keep showing that it's still attaching during that time period).

                      C 1 Reply Last reply 20 Feb 2024, 13:26
                      0
                      • C CodesInChaoss
                        20 Feb 2024, 13:25

                        As of now

                        • we are manually overriding QT's Segmentation Fault events
                        • overriding Sig33 signals (bionic hardware)

                        Under the above conditions we are able to debug through QT Creator 12 and GDB with Qt 5.15.16 BUT

                        • removal of any breakpoint causes the GDB connection to become corrupted.
                        • no further debugging would be possible

                        Anyway, we CAN live with that (hopefully).

                        The most pressing issue is - how to force the mobile app to actually wait for QT Creator to fully attach?

                        I don't know the details but it seems that QT Creator 12 attached through GDB, the app knows.. BUT... NO BREAKPOINTS WOULD FIRE FOR 2-3 minutes at all (creator would keep showing that it's still attaching during that time period).

                        C Offline
                        C Offline
                        CodesInChaoss
                        wrote on 20 Feb 2024, 13:26 last edited by
                        #53

                        We may add a Sleep for 5 minutes.. in the initial main() loop

                        but come on folks.. that is not the way we are supposed to work... is it

                        C 1 Reply Last reply 20 Feb 2024, 13:28
                        0
                        • C CodesInChaoss
                          20 Feb 2024, 13:26

                          We may add a Sleep for 5 minutes.. in the initial main() loop

                          but come on folks.. that is not the way we are supposed to work... is it

                          C Offline
                          C Offline
                          CodesInChaoss
                          wrote on 20 Feb 2024, 13:28 last edited by
                          #54
                          I System.out: Debugger has connected
                          I System.out: waiting for debugger to settle...
                          I System.out: waiting for debugger to settle...
                          I System.out: debugger detached?
                          

                          that's also present when debugging with GDB.

                          C 1 Reply Last reply 20 Feb 2024, 13:33
                          0
                          • C CodesInChaoss
                            20 Feb 2024, 13:28
                            I System.out: Debugger has connected
                            I System.out: waiting for debugger to settle...
                            I System.out: waiting for debugger to settle...
                            I System.out: debugger detached?
                            

                            that's also present when debugging with GDB.

                            C Offline
                            C Offline
                            CodesInChaoss
                            wrote on 20 Feb 2024, 13:33 last edited by
                            #55
                            Use the "info sharedlibrary" command to see the complete listing.
                            Do you need "set solib-search-path" or "set sysroot"?The index cache directory name is empty, skipping store.
                            The index cache directory name is empty, skipping store.
                            The index cache directory name is empty, skipping store.
                            Unable to find dynamic linker breakpoint function.
                            GDB will be unable to debug shared library initializers
                            and track explicitly loaded dynamic code.
                            
                            C 1 Reply Last reply 20 Feb 2024, 13:39
                            0
                            • C CodesInChaoss
                              20 Feb 2024, 13:33
                              Use the "info sharedlibrary" command to see the complete listing.
                              Do you need "set solib-search-path" or "set sysroot"?The index cache directory name is empty, skipping store.
                              The index cache directory name is empty, skipping store.
                              The index cache directory name is empty, skipping store.
                              Unable to find dynamic linker breakpoint function.
                              GDB will be unable to debug shared library initializers
                              and track explicitly loaded dynamic code.
                              
                              C Offline
                              C Offline
                              CodesInChaoss
                              wrote on 20 Feb 2024, 13:39 last edited by CodesInChaoss
                              #56

                              AFTER disabling

                              • wait for debugger in Android Developer Settings (on mobile)
                                AND
                              • after REMOVING the debugged application from the list of debugged applications ON ANDROID DEVICE

                              we are able to get have breakpoints working WAY SOONER (!!!)
                              now that i strange on the grounds of its own, is it not.....

                              but STILL unable to have breakpoints at main() stage working at all.

                              Yet again we are talking about QT Creator 12 + GDB + Qt 5.15.16 (LTS)

                              so the pressing issues are

                              • get to know how to break as soon as in main() - normal thing to be expected
                              • what the heck are sig-faults in Qt related code?
                              C 1 Reply Last reply 21 Feb 2024, 14:02
                              0
                              • C CodesInChaoss
                                20 Feb 2024, 13:39

                                AFTER disabling

                                • wait for debugger in Android Developer Settings (on mobile)
                                  AND
                                • after REMOVING the debugged application from the list of debugged applications ON ANDROID DEVICE

                                we are able to get have breakpoints working WAY SOONER (!!!)
                                now that i strange on the grounds of its own, is it not.....

                                but STILL unable to have breakpoints at main() stage working at all.

                                Yet again we are talking about QT Creator 12 + GDB + Qt 5.15.16 (LTS)

                                so the pressing issues are

                                • get to know how to break as soon as in main() - normal thing to be expected
                                • what the heck are sig-faults in Qt related code?
                                C Offline
                                C Offline
                                CodesInChaoss
                                wrote on 21 Feb 2024, 14:02 last edited by
                                #57

                                so seems like nobody (as usually) can assist around here even in questions regarding basic debugging.... this community is such a shame...

                                J T 2 Replies Last reply 21 Feb 2024, 18:15
                                0
                                • C CodesInChaoss
                                  21 Feb 2024, 14:02

                                  so seems like nobody (as usually) can assist around here even in questions regarding basic debugging.... this community is such a shame...

                                  J Offline
                                  J Offline
                                  JoeCFD
                                  wrote on 21 Feb 2024, 18:15 last edited by JoeCFD
                                  #58

                                  @CodesInChaoss Maybe try to do it on Linux and it could be easier. The executable is same.

                                  C 1 Reply Last reply 24 Feb 2024, 13:55
                                  0
                                  • C CodesInChaoss
                                    21 Feb 2024, 14:02

                                    so seems like nobody (as usually) can assist around here even in questions regarding basic debugging.... this community is such a shame...

                                    T Offline
                                    T Offline
                                    TomZ
                                    wrote on 22 Feb 2024, 10:53 last edited by TomZ
                                    #59

                                    @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

                                    so seems like nobody (as usually) can assist around here even in questions regarding basic debugging.... this community is such a shame

                                    A lot of lazy devs here ;-)

                                    I'm especially interested in Qt because of its cross-platform ability. I do 90% of my android development in a native compile, with a window on my desktop. Have had maybe once or twice the wish to have a debugger for my remote Android device, but never found it important enough to install the tools for that. Qt Android tools are too freaking huge.

                                    So, I'm lazy and debug on the native app on my desktop. Then do testing on the device, which rarely gives me issues I could not see on the desktop.

                                    Not saying that what you want is wrong or anything like that. If QtCreator tells you that breakpoints should work, then they should work. And a paying customer should be able to demand attention from the Qt company.

                                    I'm not a paying customer, no support for me.
                                    Plenty of problems with the new Qt company of the last years, gerrit sucks. Jira even more so. As an open source programmer I have zero incentive to report bugs for the LTS releases since I'd wait at minimum a full year for a bugfix. And the quality is just really quite sad for Android. But it still is better than most alternatives I've tried. So here we are :-)

                                    C 1 Reply Last reply 22 Feb 2024, 12:09
                                    0
                                    • T TomZ
                                      22 Feb 2024, 10:53

                                      @CodesInChaoss said in Unable to debug Android App (Windows + Qt Creator 12 + LLDB):

                                      so seems like nobody (as usually) can assist around here even in questions regarding basic debugging.... this community is such a shame

                                      A lot of lazy devs here ;-)

                                      I'm especially interested in Qt because of its cross-platform ability. I do 90% of my android development in a native compile, with a window on my desktop. Have had maybe once or twice the wish to have a debugger for my remote Android device, but never found it important enough to install the tools for that. Qt Android tools are too freaking huge.

                                      So, I'm lazy and debug on the native app on my desktop. Then do testing on the device, which rarely gives me issues I could not see on the desktop.

                                      Not saying that what you want is wrong or anything like that. If QtCreator tells you that breakpoints should work, then they should work. And a paying customer should be able to demand attention from the Qt company.

                                      I'm not a paying customer, no support for me.
                                      Plenty of problems with the new Qt company of the last years, gerrit sucks. Jira even more so. As an open source programmer I have zero incentive to report bugs for the LTS releases since I'd wait at minimum a full year for a bugfix. And the quality is just really quite sad for Android. But it still is better than most alternatives I've tried. So here we are :-)

                                      C Offline
                                      C Offline
                                      CodesInChaoss
                                      wrote on 22 Feb 2024, 12:09 last edited by
                                      #60

                                      Article

                                      ^------ what a F***** joke.... talked with a QT lady over phone today they ask for 3800 EURO a year (per seat) for a license with Technical Support

                                      C 1 Reply Last reply 22 Feb 2024, 12:11
                                      0
                                      • C CodesInChaoss
                                        22 Feb 2024, 12:09

                                        Article

                                        ^------ what a F***** joke.... talked with a QT lady over phone today they ask for 3800 EURO a year (per seat) for a license with Technical Support

                                        C Offline
                                        C Offline
                                        CodesInChaoss
                                        wrote on 22 Feb 2024, 12:11 last edited by CodesInChaoss
                                        #61

                                        the funniest thing of all is we've got an immense code base already so if we do not solve the issues above (LLDB - unable to debug at all) and GDB crashing all the time with all the other crazy shit going on - we would be FORCED to pay the above in HOPES they manage to give us some helpful hand.

                                        Go figure.

                                        C 1 Reply Last reply 22 Feb 2024, 12:14
                                        0
                                        • C CodesInChaoss
                                          22 Feb 2024, 12:11

                                          the funniest thing of all is we've got an immense code base already so if we do not solve the issues above (LLDB - unable to debug at all) and GDB crashing all the time with all the other crazy shit going on - we would be FORCED to pay the above in HOPES they manage to give us some helpful hand.

                                          Go figure.

                                          C Offline
                                          C Offline
                                          CodesInChaoss
                                          wrote on 22 Feb 2024, 12:14 last edited by
                                          #62

                                          we're just too afraid they gonna say hey see - IT WORKS WITH A HELLO WORLD

                                          C 1 Reply Last reply 22 Feb 2024, 12:21
                                          0

                                          52/169

                                          20 Feb 2024, 13:25

                                          • Login

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