Something strange
Something strange
- Subject: Something strange
- From: Steve Mills <email@hidden>
- Date: Thu, 9 Mar 2006 11:23:59 -0600
I've been trying to track down an Intel bug in release builds, so
I've added a bunch of printf's to code that gets built into a
library, which is linked into the main app. The printf's have been
working, properly spewing out to Console when running on the tester's
machine. Just now, after making some changes, they stopped working. I
know the code is being called. I inserted a SysBeep(0), and that
produces no beep. What would cause printf and SysBeep to stop working
in a linked library on Intel?
I don't know if this is related, but when I build the release build
(a Universal Binary), Xcode spits out a warning that I should
consider using -bind_at_load. I sort of understand what this flag
does, but not totally. I turned it on, but still don't get the printf
or SysBeep output.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.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