From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [linux] Always ignore restart/cancellation signals
Date: Sat, 10 Dec 2005 01:20:00 -0000 [thread overview]
Message-ID: <uhd9ije8k.fsf@gnu.org> (raw)
In-Reply-To: <20051209144651.GA12425@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 9 Dec 2005 09:46:51 -0500)
> Date: Fri, 9 Dec 2005 09:46:51 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, Dec 09, 2005 at 04:44:16PM +0200, Eli Zaretskii wrote:
> > > Date: Fri, 9 Dec 2005 09:34:52 -0500
> > > From: Daniel Jacobowitz <drow@false.org>
> > >
> > > The problem is that an application may want to register handlers for "a
> > > few" realtime signals. It seems common to count up from SIGRTMIN, so
> > > SIGRTMIN is made a runtime constant that skips those signals belonging
> > > to the implementation.
> >
> > Does this mean that ``constants aren't'', like the old joke says?
>
> Precisely! Directly above the bit Kevin quoted:
>
> #define SIGRTMIN (__libc_current_sigrtmin ())
> #define SIGRTMAX (__libc_current_sigrtmax ())
Then we should probably use these instead.
next prev parent reply other threads:[~2005-12-09 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 21:10 Daniel Jacobowitz
2005-12-09 10:39 ` Mark Kettenis
2005-12-09 11:09 ` Kevin Buettner
2005-12-09 11:26 ` Daniel Jacobowitz
2005-12-09 11:48 ` Kevin Buettner
2005-12-09 14:46 ` Eli Zaretskii
2005-12-09 20:52 ` Daniel Jacobowitz
2005-12-09 20:49 ` Daniel Jacobowitz
2005-12-09 21:55 ` Eli Zaretskii
2005-12-09 23:13 ` Daniel Jacobowitz
2005-12-10 1:20 ` Eli Zaretskii [this message]
2005-12-10 1:29 ` Daniel Jacobowitz
2005-12-10 1:29 ` Eli Zaretskii
2005-12-10 1:49 ` Mark Kettenis
2005-12-10 2:10 ` Daniel Jacobowitz
2005-12-10 4:47 ` Mark Kettenis
2005-12-10 1:34 ` Jim Blandy
2005-12-11 17:26 ` Eli Zaretskii
2006-02-20 17:01 ` Daniel Jacobowitz
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=uhd9ije8k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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