RE: debug a forked PTY process
RE: debug a forked PTY process
- Subject: RE: debug a forked PTY process
- From: "James Larcombe" <email@hidden>
- Date: Tue, 9 Mar 2010 11:25:13 -0000
- Thread-topic: debug a forked PTY process
> The process has forked and you cannot use this CoreFoundation
> functionality safely. You MUST exec(). Break on
> __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_
> THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
I have a related question regarding this message.
As far as I can tell, you can't actually set a breakpoint on that
function, because it's a private symbol, as you can see in the source:
http://www.opensource.apple.com/source/CF/CF-550.13/CFRuntime.c
What's the best recommendation here? I had a curious instance of that
warning recently but couldn't see why it was arising as we weren't
forking anywhere that I could see. DTrace is difficult to use in this
case because attaching to the process won't follow the forked process
when it is created.
Any debugging suggestions?
James
_______________________________________________
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