Re: No longer use NSLog() in Xcode 4?
Re: No longer use NSLog() in Xcode 4?
- Subject: Re: No longer use NSLog() in Xcode 4?
- From: David Duncan <email@hidden>
- Date: Thu, 15 Sep 2011 10:03:25 -0700
On Sep 15, 2011, at 9:43 AM, Jerry Krinock wrote:
> Back in one of those rambling Xcode 4 threads on July 24, Patrick William Walker wrote:
>
> "The new action triggers inside the debugger are pure freakin' gold. I haven't used NSLog() in weeks now."
>
> I can't find any documentation on "action triggers". I'd appreciate an explanation of what "action triggers" are, and how they obviate NSLog(). I hope they does not require running with breakpoints on. I generally don't turn breakpoints on unless I need them, because it typically takes tens of seconds for them to load.
If I understand correctly, they are associated with breakpoints (and I don't understand why it would take you 10s of seconds to turn them on, but that would probably make a worthy bug report).
When you edit a breakpoint, you can add an action to log a message and then set the breakpoint to continue automatically afterwards, which gives you the basic equivalent of adding logging at various issues but only while debugging.
You can also do lots of other things like automatically run various debugging commands, shell commands, play sounds, etc. If you issue a debugging command however, you will have to add another action to 'continue' the debugger (if you wish the breakpoint to continue) due to a bug in GDB.
--
David Duncan
_______________________________________________
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