Understanding backtraces in Google Play Console
-
Hello,
In Google Play Console, I have backtraces that I can't understand, like :
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** pid: 0, tid: 21857 >>> net.test <<< backtrace: #00 pc 0x000000000008a0d4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) #01 pc 0x0000000000045b88 /apex/com.android.runtime/lib64/bionic/libc.so (free+96) #02 pc 0x0000000000220308 /data/app/~~j88M7vCssnoC0vnYTkcNbA==/net.test-XbZqTMoJQhwU33E2CodCpg==/lib/arm64/libtest_arm64-v8a.so (QTest:closeEvent(QCloseEvent*)+780) #03 pc 0x00000000001c72bc /data/app/~~j88M7vCssnoC0vnYTkcNbA==/net.test-XbZqTMoJQhwU33E2CodCpg==/lib/arm64/libQt5Widgets_arm64-v8a.so (QWidget::event(QEvent*)+124)What do the numbers after the functions mean? For example closeEvent(QCloseEvent*)+780
How to find the corresponding line in my code?
Thank you for your help!
-
Hello,
In Google Play Console, I have backtraces that I can't understand, like :
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** pid: 0, tid: 21857 >>> net.test <<< backtrace: #00 pc 0x000000000008a0d4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) #01 pc 0x0000000000045b88 /apex/com.android.runtime/lib64/bionic/libc.so (free+96) #02 pc 0x0000000000220308 /data/app/~~j88M7vCssnoC0vnYTkcNbA==/net.test-XbZqTMoJQhwU33E2CodCpg==/lib/arm64/libtest_arm64-v8a.so (QTest:closeEvent(QCloseEvent*)+780) #03 pc 0x00000000001c72bc /data/app/~~j88M7vCssnoC0vnYTkcNbA==/net.test-XbZqTMoJQhwU33E2CodCpg==/lib/arm64/libQt5Widgets_arm64-v8a.so (QWidget::event(QEvent*)+124)What do the numbers after the functions mean? For example closeEvent(QCloseEvent*)+780
How to find the corresponding line in my code?
Thank you for your help!
@Francky033
I think they are "offsets" into the specified function. If you were lucky they would be source line numbers, but I suspect they are not (no source code/not compiled for debug) and are just the byte offset from start of function to the statement it was executing. And I don't think there is any way of mapping that back to a line number, unless you want to look at the disassembly and figure out what that corresponds to in the source. -
@Francky033
I think they are "offsets" into the specified function. If you were lucky they would be source line numbers, but I suspect they are not (no source code/not compiled for debug) and are just the byte offset from start of function to the statement it was executing. And I don't think there is any way of mapping that back to a line number, unless you want to look at the disassembly and figure out what that corresponds to in the source.Thanks @JonB for the precisions. I am using Android Studio to identify the lines of code, and it seems to work. Thanks!
