Re: preventing delivery of Signals.
Re: preventing delivery of Signals.
- Subject: Re: preventing delivery of Signals.
- From: Eric Tilton <email@hidden>
- Date: Thu, 14 Feb 2002 09:07:41 -0600
Yes, the debugger can (and will, by default) stop when a signal is
delivered, even if your app is ignoring that signal. You can use
info signals
to see how this is configured, and
handle <signal> <keywords>
to change the configuration so that gdb will ignore the signal too (use
"help handle" for the lowdown).
enjoy,
eric
On Thursday, February 14, 2002, at 08:03 AM, cocoa-dev-
email@hidden wrote:
Message: 7
Date: Thu, 14 Feb 2002 12:12:25 +0100
Subject: Re: preventing delivery of Signals.
Cc: email@hidden, email@hidden
To: Eric Seidel <email@hidden>
From: Marcel Weiher <email@hidden>
On Thursday, February 14, 2002, at 09:43 AM, Eric Seidel wrote:
The problem arises that I have a multithreaded application (only 2
threads) and the SIGPIPE signal seems to get delivered to the PROCESS
and not the THREAD.
Yes, this is how it works in Darwin/OS X.
when I tried signal(SIGPIPE, SIG_IGR) or sigignore(SIGPIPE), or even
sigaction(...) to ignore the signal from one thread, it still got
delivered... and I got stopped in the debugger.
Beware of the debugger. I think it will 'see' signals even if your
program is ignoring them.
Marcel
--
Marcel Weiher Metaobject Software Technologies
email@hidden www.metaobject.com
Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.