Open PaulDance opened 10 months ago
Here's some code you could take for the implementation: https://github.com/mstange/macho-stubs/blob/6dbb225e43002afe97a539682bbba731029c0fc9/src/main.rs#L140-L298
(see #377 for my use case)
I was initially going to simply port it from mach_object
, but this should indeed prove to be another source of inspiration. Thanks!
Mach-O objects can contain a dyld info command that points to various data structures. Among those is the generic, weak and lazy binding info that store the set of symbol information to be imported upon loading by
dyld
, if I understand things correctly.Parsing such data is really not trivial, as it involves traversing through various operation codes that gradually build symbols one by one, so having it in
object
would be nice. Currently, themach_object
crate offers a correct implementation: I've been using it for a work project and it seems to behave well. However, this crate does not seem to be maintained anymore and the maintainer seems unreachable. We would therefore gladly work on porting the functionality toobject
instead and therefore upstream part of our work.A few questions about the contribution then:
object
?macho
vs.read::macho
? There aren't much definitions similar to the rest ofmacho
, it's mostly the parsing algorithm that needs implementation.MachOFile
or to theObject
trait and its implementation of it? Having it outside of the trait makes more sense to me because it would not be behavior common to all formats, but I'm just checking anyways.