Any suggestions for localizing a linker crash?
Any suggestions for localizing a linker crash?
- Subject: Any suggestions for localizing a linker crash?
- From: Jay Reynolds Freeman <email@hidden>
- Date: Fri, 15 Oct 2010 13:15:54 -0700
I have a problem with linking a 64-bit library that I have created,
with a 64-bit app (also mine) that needs to use it, all in Xcode 3.2.4,
running on a MacPro3,1 under MacOS 10.6.4. The library builds and
links fine, and all files of the app compile properly, but then the
linker (ld) itself crashes with EXC_BAD_ACCESS (SIGSEGV), and I have
crash logs and so on.
To add insult to injury, when I modify my app to include all the files
that are in the library, and then remove the linkage step to the
library, the whole thing compiles, links, and runs just fine.
I suspect this is a bug worth reporting, but my app is large, and so
is my library, and I have been unable to come up with a smaller example
to submit as part of a bug report. I am rather unfamiliar with the
details of how ld operates -- I have pretty much used it as a black
box, letting Xcode figure out how to invoke it -- so I am not sure
what to do to trim things down.
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?
Internet search turns up nothing obviously related to this bug.
Thanks!
-- Jay Reynolds Freeman
---------------------
email@hidden
http://web.mac.com/jay_reynolds_freeman (personal web site)
_______________________________________________
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