From: Simon Kirby <sim@netnation.com>
To: Philippe Troin <phil@fifi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strangeness with signals
Date: Tue, 27 Sep 2005 20:47:00 -0700 [thread overview]
Message-ID: <20050928034659.GA27953@netnation.com> (raw)
In-Reply-To: <87hdc6htur.fsf@ceramic.fifi.org>
On Tue, Sep 27, 2005 at 06:19:24PM -0700, Philippe Troin wrote:
> The SIGWINCH and SIGCHLD signals are not generated if their
> disposition is set to SIG_DFL. I believe SIGCONT and SIGURG also
> behave similarly. If you want to see them from your application, you
> have to establish a (potentially empty) signal handler.
Ok, and this is what I did in the example; however, is it expected that
it does not help to set a handler in sa_handler and call sigaction()?
In fact, it does not matter what sa_handler is set to (it can still be
SIG_IGN), but sa_sigaction must point to a valid handler.
Simon-
next prev parent reply other threads:[~2005-09-28 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 23:20 Strangeness with signals Simon Kirby
2005-09-28 1:19 ` Philippe Troin
2005-09-28 3:47 ` Simon Kirby [this message]
2005-09-28 15:30 ` Philippe Troin
2005-09-28 18:00 ` Simon Kirby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050928034659.GA27953@netnation.com \
--to=sim@netnation.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@fifi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).