Re: Dwarf and comparing binaries
Re: Dwarf and comparing binaries
- Subject: Re: Dwarf and comparing binaries
- From: Peter O'Gorman <email@hidden>
- Date: Sat, 24 Nov 2007 13:57:35 -0600
Jonas Maebe wrote:
> Hello,
>
> It seems that every time you compile a binary with Dwarf debug info, it
> ends up being slightly different. I guess the linker includes some time
> stamps of the object files or some such in the final binary. Is there a
> way to avoid this? Running dsymutil doesn't help.
>
> The reason I'm asking is that when compiling our compiler, it compiles
> itself up to a maximum of three times and if the generated binaries then
> still don't match, the makefile assumes there's an insidious code
> generator error somewhere (insidious because the compiler didn't crash,
> yet still generated different code every time).
>
> The result is that it is currently impossible to compile our compiler
> and all packaged units with dwarf info under Mac OS X, as the makefile
> will fail during that process. It's of course possible to manually
> compile everything separately, but that's quite annoying.
>
> FWIW: everything works fine with stabs, and also with dwarf on other
> platforms (but there the linker simply embeds the dwarf debug info in
> the binary rather than keeping it in separate object file).
The linker adds a UUID to the object files. Try adding -no_uuid to the
link flags. You might need to -Wl,-no_uuid, I have not checked if gcc
passes the flag through.
Peter
--
Peter O'Gorman
http://pogma.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden