Re: PATCH: Fix SIGRTMIN problems with glibc 2.3 [1/2]

[Andreas Schwab <schwab@suse.de>]

Daniel Jacobowitz <drow@mvista.com> writes:

|> Index: signals.c
|> ===================================================================
|> RCS file: /cvs/src/src/gdb/signals/signals.c,v
|> retrieving revision 1.5
|> diff -u -p -r1.5 signals.c
|> --- signals.c	27 Aug 2002 22:37:14 -0000	1.5
|> +++ signals.c	26 Mar 2003 16:25:51 -0000
|> @@ -30,6 +30,20 @@
|>  
|>  #include <signal.h>
|>  
|> +/* Always use __SIGRTMIN if it's available.  SIGRTMIN is the lowest
|> +   _available_ realtime signal, not the lowest supported; glibc takes
|> +   several for its own use.  */
|> +
|> +#ifndef REALTIME_LO
|> +# if defined(__SIGRTMIN)
|> +#  define REALTIME_LO __SIGRTMIN
|> +#  define REALTIME_HI __SIGRTMAX
|> +# elif defined(SIGRTMIN)
|> +#  define REALTIME_LO __SIGRTMIN
|> +#  define REALTIME_HI __SIGRTMAX
                          ^^
Typo?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."