This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Universal Mach-O target for BFD

From: John Reiser <jreiser at bitwagon dot com>
To: binutils at sourceware dot org
Date: Thu, 08 Oct 2009 17:23:31 -0700
Subject: Re: Universal Mach-O target for BFD
References: <B13FDB79-489E-4D9F-8F28-2BE899AA1D92@gmail.com>

c. A 4-byte offset from the beginning of the file to the start of the
Mach-O header for the object file.
d. A 4-byte size of the object file, in octets.

I'd be glad to try my hand at implementing it; does anyone have any
pointers for where to get started?


Assuming that clients access only within the interval that is designated
by the header information (and don't go snooping to discover what is
behind the curtains), then it is enough to virtualize lseek() and mmap()
in order to "relocate" the offsets into the file.

--

References:
- Universal Mach-O target for BFD
  - From: Ryan Govostes

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]