Re: Why Is NSLog a No-Op?
Re: Why Is NSLog a No-Op?
- Subject: Re: Why Is NSLog a No-Op?
- From: Quincey Morris <email@hidden>
- Date: Sat, 19 Dec 2009 15:46:10 -0800
On Dec 19, 2009, at 15:18, Thomas Wetmore wrote:
> I've reached an impasse on something that seems trivial. I am Running Xcode 3.2.1 on Mac OS X 10.6.2 with "Overview" equal to "10.6|Debug|i386" on a 24" iMac 2.66 GHz Intel Core 2 Duo.
>
> I have a foundation command line tool that calls a static cocoa library. Both were built with the same "Overview."
>
> When running or debugging the program all calls to NSLog in the command line project's code work, but all calls to NSLog from the static library code are no-ops.
Are you literally claiming that the library's calls to NSLog are no-ops? That is, do you mean that in the compiled code, the calls to the NSLog function are not there and/or have be replaced by assembly level NOP instructions? Or do you simply mean that the NSLog calls appear to do nothing?
Since you say you are compiling the library from source code, it seems like you could set a breakpoint at a NSLog call, and when you get there examine the assembly code.
I'm wondering if in fact the problem is not that there are no calls to NSLog, but that something has caused the format string literal references to be lost and so your library code is actually passing nil as the first NSLog parameter. You should be able to determine that when you hit the breakpoint, too.
_______________________________________________
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