-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symbolication misses entries in Application Specific Backtrace #25
Comments
Thanks for the detailed report! It seems when scanning the backtrace, taking the frames that have an address is not enough. We need to also match names from the Binary Images section. I'm very curious about why the crash log looks like that though. Would you mind sharing the Binary Images section? This part specifically: I'm trying to see if there are two entries ( (Sidenote: If it's just one, you can replace This would be really helpful for the fix. Thanks! 🙏 |
Below is the beginning of the crash report up until the first half dozen binary images. So the only relevant binary image I see listed is "com.ajnaware.Astro-Gold", which would explain why the symbolication doesn't work on the "Astro Gold" entries. But I am certainly puzzled as to why there are two separate items that need to be somehow recognised as pointing to the same binary. Makes me wonder if there is something strange about my project configuration. =============================== Process: Astro Gold [709] Date/Time: 2021-10-07 13:49:40.414 -0300 Time Awake Since Boot: 630 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Termination Signal: Illegal instruction: 4 Application Specific Information: Application Specific Backtrace 1: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.NSURLConnectionLoader Thread 2:: com.google.firebase.crashlytics.MachExceptionServer Thread 3:: com.apple.NSEventThread Thread 4: Thread 5: Thread 6: Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 2 Binary Images: |
Thanks for sharing! So it's not multiple binary images like I initially guessed. The complete crash report made me notice that it's in the "Application Specific Backtrace" section, and not "Thread N". I think it just displays differently when it's under "Application Specific Backtrace". The fix will have to match frames using the process name. I will close this ticket once the update is released 👍 |
Thanks for reporting this and providing all the helpful information, and sorry it took so long to get back to it. This should be fixed with MacSymbolicator 2.6. Please give it a try and create a new issue if you see any problems. |
I am running MacSymbolicator 2.3 (5)
When analyzing a crash report it symbolicates items from a thread, but misses items in main backtrace (items "Astro Gold"). My best guess as to why this happens is some problem with regex matching causing the entries in the main backtrace to be missed.
This is the log generated by the app:
Searching Spotlight for UUIDs: ["F6CBD55D-BEF2-3C06-9950-9B36D48695C4"]
Found F6CBD55D-BEF2-3C06-9950-9B36D48695C4: /Users/gpdawson/Library/Developer/Xcode/Archives/2021-10-06/Astro Gold 6-10-21, 8.43 am.xcarchive/dSYMs/Astro Gold.app.dSYM
Running command: xcrun atos -o "/Users/gpdawson/Library/Developer/Xcode/Archives/2021-10-06/Astro Gold 6-10-21, 8.43 am.xcarchive/dSYMs/Astro Gold.app.dSYM/Contents/Resources/DWARF/Astro Gold" -arch x86_64 -l 0x100a49000 0x0000000100c74d2a 0x0000000100c76b13
STDOUT: FIRCLSSDKFileLog (in Astro Gold) (FIRCLSInternalLogging.c:0)
FIRCLSMachExceptionServer (in Astro Gold) (FIRCLSMachException.c:170)
STDERR:
Replacing matches in sample report: []
Replacing matches in crash report: ["0x0000000100c74d2a 0x100a49000 + 2276650"]
Replacing matches in sample report: []
Replacing matches in crash report: ["0x0000000100c76b13 0x100a49000 + 2284307"]
Two relevant extracts from crash file are as follow.
Application Specific Information:
Crashing on exception: *** -[__NSArrayM objectAtIndex:]: index 14 beyond bounds [0 .. 12]
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff420bff3b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff69418942 objc_exception_throw + 48
2 CoreFoundation 0x00007fff420fffcc _CFThrowFormattedException + 194
3 CoreFoundation 0x00007fff41fe1faf -[__NSArrayM objectAtIndex:] + 175
4 Astro Gold 0x0000000100b74ad0 Astro Gold + 1227472
5 Astro Gold 0x0000000100a942cb Astro Gold + 307915
6 AppKit 0x00007fff3fe75f29 _NSViewDrawRect + 83
7 AppKit 0x00007fff3fe831c4 -[NSView(NSInternal)
Thread 2:: com.google.firebase.crashlytics.MachExceptionServer
0 libsystem_kernel.dylib 0x00007fff6a1856fa write + 10
1 com.ajnaware.Astro-Gold 0x0000000100c74d2a 0x100a49000 + 2276650
2 com.ajnaware.Astro-Gold 0x0000000100c76b13 0x100a49000 + 2284307
3 libsystem_pthread.dylib 0x00007fff6a34b661 _pthread_body + 340
4 libsystem_pthread.dylib 0x00007fff6a34b50d _pthread_start + 377
5 libsystem_pthread.dylib 0x00007fff6a34abf9 thread_start + 13
The text was updated successfully, but these errors were encountered: