Philip Craig

Mach-O files are supported, but addr2line doesn't know how to locate the dsym. You need to specify it instead of the executable.

Is that a multi-architecture (fat) binary? We don't currently handle them in the object crate. I don't think it would be hard to fix, but not something I've looked into....

I've got some code in [`ddbug`](https://github.com/gimli-rs/ddbug/blob/master/main/src/code.rs#L75) that uses capstone to disassemble instructions to find calls, and a copy in [`findpanics`](https://github.com/philipc/findpanics/) too. It's currently incomplete, but I'm working on updating it....

https://github.com/rust-embedded/cross is easy to use. It runs tests using qemu.

In addition to the parsing, there's a lot of overhead in iteration over attributes and returning a value for each one. The user needs to be able to define for...

I think these augmentation extensions are something that we need to add explicit support for, rather than letting you directly set the string, because some augmentation characters require special handling....

Unfortunately it's a bit hard to work out the cause of the `InvalidAttributeValue` without doing some debugging, since there's a few places that can generate it. You could modify gimli...

> I noticed that object library worked fine with a relocatable object file but had issues with an executable file(couldn't reproduce all the contents and couldn't create an executable file)....

Ok okay, yeah I am getting the `InvalidAttributeValue` for that one. I'll look into it.

It's the `DW_AT_GNU_locviews` attribute, which we don't support converting or writing yet.