Another thing: A lot of system libraries on recent versions of macOS are universal files that have binaries for two different 64-bit architectures -- x86_64 and x86_64h (the 'h' stands for Haswell). Each has its own set of symbols. /usr/lib/libobjc.dylib on 10.15 is an example. I assume our scripts and Socorro can deal with this. Am I right? Many of the non-symbolicated crash stacks that I've looked at recently (particularly for 10.15) contain addresses that must be in the Haswell binaries (the addresses only make sense there).
Bug 1588843 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Another thing: A lot of system libraries on recent versions of macOS are universal files that have binaries for two different 64-bit architectures -- x86_64 and x86_64h (the 'h' stands for Haswell). Each has its own set of symbols. /usr/lib/libobjc.dylib on 10.15 and 10.14 is an example. I assume our scripts and Socorro can deal with this. Am I right? Many of the non-symbolicated crash stacks that I've looked at recently (particularly for 10.15) contain addresses that must be in the Haswell binaries (the addresses only make sense there).