This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [linux] Always ignore restart/cancellation signals


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]