Application reports file does not need symbolicating, is not symbolicated

inket / MacSymbolicator

Symbolicating macOS/iOS crash reports, easily.

GNU General Public License v2.0

1.25k stars 91 forks source link

Application reports file does not need symbolicating, is not symbolicated #45

Closed GNUGradyn closed 1 week ago

GNUGradyn commented 3 months ago

Here is the log I am attempting to debug. I copy/pasted it from a modal that was the result of a mysterious install-time crash I have been trying to fix.

log.crash.txt

It is clearly not symbolicated but the app reports that it is. Trying to proceed anyway just results in an empty output

RichardTea commented 1 month ago

The attached "log.crash.txt" file is not in a supported format.

There are no Processes listed in the file, so there's nothing it can symbolicate
Additionally, there are no Binary Images listed in the file, so it is not possible to search for dSYMs

The bug looks to be that ReportFile doesn't throw an InitializationError if an incompatible file doesn't start with '{'

What generated the file? Possibly this should become a feature request

burzumumbra commented 2 weeks ago

I'm having the same issue with a .crash file :/

inket commented 1 week ago

@RichardTea is right here. The attached text file is not a crash report, but it seems to be an error report generated by Xcode.

This is an error that happened within one of Xcode's components and it's spitting out the log so that you can give it to Xcode's developers at Apple. It is not meant for you. (You do not have the DSYMs to symbolicate it anyway)

@burzumumbra Please create a separate issue and share your crash report file.