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. Stack traces and code source
Forum Update on Monday, May 27th 2025

Stack traces and code source

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
7 Posts 2 Posters 808 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.
  • F Offline
    F Offline
    Francky033
    wrote on 16 Nov 2020, 12:39 last edited by
    #1

    I would like to analyse the Stack Traces information that is present in the Google Play Console but I can't do it.

    I compiled the apk with the "-DEBUG" parameter and then opened the apk file in Android Studio, but when I paste the stack trace into the "stack trace or thread dump" tool in Android Studio everything appears in red and I can't display any hyperlinks to my source code.

    I would like to know, for example, which line of the code corresponds to "processCalculs()+94776".

    How to do this?

    With my thanks,

    Franck

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    pid: 0, tid: 0 >>> net.XXXXXX <<<
    
    backtrace:
      #00  pc 00000000001f8234  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libWinStars3_arm64-v8a.so (QXXXXXXView::processCalculs()+94776)
      #00  pc 00000000002ff344  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libWinStars3_arm64-v8a.so
      #00  pc 000000000021405c  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libQt5Core_arm64-v8a.so
      #00  pc 0000000000218d10  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libQt5Core_arm64-v8a.so (QTimer::timeout(QTimer::QPrivateSignal)+56)
      #00  pc 000000000020cd30  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libQt5Core_arm64-v8a.so (QObject::event(QEvent*)+120)
      #00  pc 000000000018fe88  /data/app/net.XXXXXX-GoGDvRdK5EFbUfuQgLSrXA==/lib/arm64/libQt5Widgets_arm64-v8a.so (QApplicationPrivate::notify_helper(QObject*, QEvent*)+304)
    
    1 Reply Last reply
    0
    • F Offline
      F Offline
      Francky033
      wrote on 16 Nov 2020, 16:11 last edited by
      #2

      Another way of asking the question, perhaps a bit clearer?

      Is there an easy way to find the line in the source code corresponding to QXXXXXXView::processCalculs()+94776?

      Thanx!

      J 1 Reply Last reply 16 Nov 2020, 19:15
      0
      • F Francky033
        16 Nov 2020, 16:11

        Another way of asking the question, perhaps a bit clearer?

        Is there an easy way to find the line in the source code corresponding to QXXXXXXView::processCalculs()+94776?

        Thanx!

        J Offline
        J Offline
        JonB
        wrote on 16 Nov 2020, 19:15 last edited by
        #3

        @Francky033
        I know nothing about Google/Android development. But for desktops you have to have the source files available, and the IDE/debugger has to know where they are, for the code function offsets to be shown as corresponding line of source.

        1 Reply Last reply
        0
        • F Offline
          F Offline
          Francky033
          wrote on 17 Nov 2020, 00:51 last edited by Francky033
          #4

          Thank you JonB!

          Yes, I can now load the apk with the source code. But nothing happens when I paste the backtrace obtained in Google console in the "stack trace or thread dump" tool of Android Studio.
          In my case, the +94776 that appears behind the processCalculs() function does not correspond to a line number. I rather think it is the number of bytes between the beginning of the function and the crash.

          But I don't know how to exploit these damn stacktraces.

          J 1 Reply Last reply 17 Nov 2020, 23:45
          0
          • F Francky033
            17 Nov 2020, 00:51

            Thank you JonB!

            Yes, I can now load the apk with the source code. But nothing happens when I paste the backtrace obtained in Google console in the "stack trace or thread dump" tool of Android Studio.
            In my case, the +94776 that appears behind the processCalculs() function does not correspond to a line number. I rather think it is the number of bytes between the beginning of the function and the crash.

            But I don't know how to exploit these damn stacktraces.

            J Offline
            J Offline
            JonB
            wrote on 17 Nov 2020, 23:45 last edited by
            #5

            @Francky033
            Again, I don't know the exact process for you/Android. You do not "paste a stack trace". The idea is to run your program from a debugger, which knows where the sources both to the program and for the system libraries are located, and let the program "crash". At that point the debugger will see the fault and halt the program. When you then go into the debugger's "stack trace window" the addresses you show will be resolved to the matching lines in the source file.

            That's how it works on desktop....

            1 Reply Last reply
            0
            • F Offline
              F Offline
              Francky033
              wrote on 18 Nov 2020, 08:25 last edited by
              #6

              Actually, the problem is that I'm trying to debug crashes that happen on some users' mobiles. But most of the time, these are crashes that I can't reproduce on my own mobile.
              So I have to be able to associate a line of the source code with the offset that appears in the stack traces of Google..... This is the point I can't do....

              J 1 Reply Last reply 18 Nov 2020, 09:32
              0
              • F Francky033
                18 Nov 2020, 08:25

                Actually, the problem is that I'm trying to debug crashes that happen on some users' mobiles. But most of the time, these are crashes that I can't reproduce on my own mobile.
                So I have to be able to associate a line of the source code with the offset that appears in the stack traces of Google..... This is the point I can't do....

                J Offline
                J Offline
                JonB
                wrote on 18 Nov 2020, 09:32 last edited by
                #7

                @Francky033
                I can only say: if you are not receiving an answer here, your question is about Android and stack traces in general, nothing to do with Qt. So you would be better searching some "Android development" posts/forums.

                1 Reply Last reply
                0

                1/7

                16 Nov 2020, 12:39

                • 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