Re: Finding a spurious console message
Re: Finding a spurious console message
- Subject: Re: Finding a spurious console message
- From: Jonas Maebe <email@hidden>
- Date: Thu, 13 Mar 2008 18:32:12 +0100
On 13 Mar 2008, at 17:44, Matt Gough wrote:
Somewhere in my app, something is writing a spurious message to the
console that is probably only meant for debugging purposes.
(Unfortunately there is no context to the string, its just a number
with no explanation) I have tried putting breakpoints at printf,
NSLog and CFLog but it does not appear to be using one of those.
Is there a single (or small set of ) bottleneck that all console
printing goes through so I can set appropriate breakpoints.
write. If you debug on ppc, you can probably use this:
break write cond ($r3 == 1) || ($r3 == 2)
(r3 contains the file descriptor for write, and the default file
descriptor for standard output is 1 and for standard error it's 2).
For x86, the arguments are on the stack and how you have to access
them depends on whether or not that function has a stack frame, which
I don't know by heart.
Jonas
_______________________________________________
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