This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: libc 2.3 and RT signals broken
- From: Andreas Schwab <schwab at suse dot de>
- To: libc-alpha at sources dot redhat dot com
- Cc: debian-glibc at lists dot debian dot org
- Date: Tue, 29 Oct 2002 09:52:54 +0100
- Subject: Re: libc 2.3 and RT signals broken
- References: <20021029024019.GA471@nevyn.them.org>
Daniel Jacobowitz <dan@debian.org> writes:
|> SIGRTMIN has changed behavior recently in 2.3; at the same time as:
|>
|> 2002-09-18 Ulrich Drepper <drepper@redhat.com>
|>
|> * signal/allocrtsig.c: Move to...
|> * sysdeps/generic/allocrtsig.c: ...here. New file.
|>
|> as far as I can tell.
|>
|> The problem is something I ran into in GDB today: the location of a
|> source file overrides the normal search path. If a file in
|> sysdeps/generic/ includes a header using "", the copy in
|> sysdeps/generic/ will win. So we get sysdeps/generic/testrtsig.h
|> instead of the sysdeps/unix/sysv/linux/testrtsig.h, and
|> kernel_has_rtsig always returns 0.
The right fix is probably to change "..." to <...>. Could you try that
please?
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."