Re: Any suggestions for localizing a linker crash?
Re: Any suggestions for localizing a linker crash?
- Subject: Re: Any suggestions for localizing a linker crash?
- From: Greg Guerin <email@hidden>
- Date: Fri, 15 Oct 2010 15:26:18 -0700
Jay Reynolds Freeman wrote:
Does anyone have any suggestions for things I could do to get more
information, or perhaps to localize the bug to a subset of the
relevant source code, before I submit a bug report to Apple?
Put half the library functions in a library, and half compiled with
the app. The division is arbitrary, so do it in the easiest way. If
it works, exchange the halves.
If both halves work in both location, then split each half and repeat
recursively. The idea is to have 3/4 in the lib after the second
halving, and rotate each 1/4 into the app. At some point you'll have
nearly all the lib functions in the lib, or you'll have a crash with
a subset. This is basically binary search or binary space partitioning.
You didn't say whether it's a static lib or a dylib. Try it both
ways. Try it with a 32-bit arch (if practical).
Ttry rearranging the link order of the functions in the lib. If a
dylib, arrange the link order differently by listing .o files in
alternate order. If a static lib, use the 'ar' command manually.
-- GG
_______________________________________________
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