Re: App Crashes when ZeroLink isn't Used
Re: App Crashes when ZeroLink isn't Used
- Subject: Re: App Crashes when ZeroLink isn't Used
- From: j o a r <email@hidden>
- Date: Thu, 14 Sep 2006 19:39:55 +0200
On 14 sep 2006, at 19.32, Nate Slater wrote:
I'm trying to fix a crash in an open-source cocoa app. The app
splits MP3 files into pieces. I'm not the programmer or maintainer.
When I make a development (debug) build using ZeroLink everything
works fine with no errors or warnings. However when I build the app
without ZeroLink, it links just fine but the app crashes with an
EXC_BAD_ACCESS exception as soon as it starts to analyze an MP3 file.
What warnings, if any, do you get when compiling?
The search paths used to include an entry to an id3lib folder in
the programmer's home directory in addition to the previous entries
I mentioned. Why is this? Also in the main target (there's only
one), under "Link Binary With Libraries", there were two entries
for libid3.dylib with the exact same file locations (the project
folder). Why Would Xcode need to link the exact same library twice?
What happens if you remove / change these settings?
Another complication is that I have a copy of id3lib with the same
version in my /sw tree. However, when I do a binary compare of the
dylib in /sw and the one in my project folder, they have numerous
differences. Could ZeroLink be loading one library while the Xcode
linker loads another?
That should be easy to verify, don't you agree?
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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