Re: Something strange
Re: Something strange
- Subject: Re: Something strange
- From: Rush Manbert <email@hidden>
- Date: Thu, 09 Mar 2006 12:29:04 -0800
Steve Mills wrote:
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.
I have had similar problems, but I'm only building and running on PPC. I
have had printfs that stopped working, and I have also had couts that
stopped working. That was what I saw first. I changed them to printfs
and they started working again, but I know that I also have printfs that
don't seem to do anything, even though I know from the debugger that I
execute the code.
I believe that I have only seen this in C++ code, not Objc.
Can you get into trouble like this if you mix printf & cout in your code?
- Rush
_______________________________________________
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