Debugging a macOS IPS dump

Question

Created 2w

Replies 1

Boosts 0

Participants 2

I have a macOS application built via command line (xcodebuild) using Xcode 16.1. Developed on ARM but end user is on Intel (same macOS 15.1).

App crashed and they sent me a .IPS dump.

From what MacGPT tells me: Reading an IPS (Incident Processing System) file from a macOS crash report in Xcode isn’t as straightforward as with iOS device logs.

I can open the dump using Console. I see the IPS dump is partially symbolicated.

Line in the dump says: Meteorologist 0x103e0348f 0x103d88000 + 504975

Referencing this article: Adding identifiable symbol names to a crash report | Apple Developer Documentation

I run this command and see the same UUID for x86_64 as in the dump.

dwarfdump --uuid /Users/ed/meteorologist/trunk/Build/Meteorologist.xcarchive/dSYMs/Meteorologist.app.dSYM/Contents/Resources/DWARF/Meteorologist

I run this command:

atos -arch x86_64 -o /Users/ed/meteorologist/trunk/Build/Meteorologist.xcarchive/dSYMs/Meteorologist.app.dSYM/Contents/Resources/DWARF/Meteorologist -l 0x103d88000 0x103e0348f

And it says: fg: no current job

Suggestions for what I’m missing?

Boost

Answer 1

DTS Engineer OP

Apple

2w

And it says: fg: no current job

You're on the right path, and the commands you provided above look correct to my eye, short of verifying the actual addresses you're passing in from your crash report.

I've never seen that specific error text before. It sounds like that could be a shell-level error, such as if you've customized Terminal beyond the basics. Is there anything like that in play for you?

One other way to symbolicate the crash report that is helpful is this command:

xcrun crashlog /path/to/crash.ips

This runs LLDB to locate the matching dSYM file automatically on macOS and then output the symbolicated crash report, including breaking apart any inlined code in a way that atos won't do without using an -i argument in the command.

— Ed Ford,  DTS Engineer

0