Re: mach-o section question
Re: mach-o section question
- Subject: Re: mach-o section question
- From: Jason Molenda <email@hidden>
- Date: Mon, 21 Apr 2008 14:35:47 -0700
Cem,
On Apr 21, 2008, at 5:35 AM, Army Research Lab wrote:
5) The uuid_command referenced on page 20 uses a 128 bit UUID; is this
expected to be the output of uuid_generate(), or will any 128 bit UUID
generator work (in short, is there hidden info in the UUID that I
need to
keep straight)?
The uuid_generate family of functions is fine. The content of the
LC_UUID load command is primarily intended to tie an executable binary
to its matching debug info dSYM bundle unambiguously. Computing some
digest of the binary, like an MD5, is also fine. Using an MD5 will
add time to your file generation but it does mean that two binaries
with the same contents will have the same LC_UUID which may be helpful
depending on your build environment.
An example of how this can be useful: A Spotlight importer is
included in Leopard which indexes the LC_UUIDs of all the dSYMs in its
search space. When you run the debugger on an executable, it can do a
Spotlight query to find the matching dSYM bundle debug info
automatically.
J
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden