How to get a bigger stacktrace



  • I get some crash reports from Google Play with only a single line in the backtrace. This is not a 'root' function so the stacktrace should be bigger. Is there a way (different compile options?) to get a bigger stacktrace?
    FWIW, the crashes (currently) occur on two devices, both running Android 9

    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    pid: 0, tid: 0 >>> com.xxx.yyy <<<
    
    backtrace:
      #00  pc 0000000000080bee  /data/app/com.xxx.yyy-ZqFsiKjv33JpJct6CfC72w==/lib/arm/libAppZZZ.so (some_function+232)
    

  • Qt Champions 2017

    Using a debug build should provide you with more. As I assume this is a release build for distribution, then perhaps a release with debug info (what is usually done for profiling) is a compromise of sorts.



  • For testing purposes, I trigger a segfault myself.
    When I run this code on Linux I get a complete stacktrace
    When I run this on Android (debug and release mode) I just get one frame in the "./adb logcat -b crash" output
    Any ideas?


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.