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


On Thu, 8 Dec 2005 20:50:09 +0100 (CET)
Mark Kettenis <mark.kettenis@xs4all.nl> wrote:

> > Date: Thu, 8 Dec 2005 09:24:20 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > The comment is fairly self-explanatory.  I guess I've always debugged
> > failing cancellation tests with gdbserver, which hardwires these values
> > already...
> > 
> > Any objections?
> 
> Hmm, I thought symbols starting with __ were "reserved by the
> implemntation" and should not be used by user space programs.

For the symbols in question, the header file, <bits/signum.h>, says:

    /* These are the hard limits of the kernel.  These values should not be
       used directly at user level.  */
    #define __SIGRTMIN	32
    #define __SIGRTMAX	(_NSIG - 1)

So the comment supports your claim.

The only alternative that I can think of is to hardcode the constant
(32, in this case) into the GDB sources.  Of these two approaches, I'd
prefer to use __ symbol from the system headers.  I do think that we
ought to check for its existence first though.

Kevin


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