This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/184] New: sighold() receives SIGSEGV when called with invalid signal
- From: "alan dot johnston at gd-ais dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 27 May 2004 16:26:57 -0000
- Subject: [Bug libc/184] New: sighold() receives SIGSEGV when called with invalid signal
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
The SourceForge Open POSIX test suite performs end case tests where sighold()
is called with invalid signal numbers. Instead of returning EINVAL, the
process receives a SIGSEGV.
The problem occurs because sighold.c calls __sigaddset(), which is an unchecked
sigaddset() call. Since the invocation of sighold() is using an invalid signal
number, __sigaddset assuming the signal is valid, gets a memory reference error.
sighold.c should b call sigaddset(), not __sigaddset().
--
Summary: sighold() receives SIGSEGV when called with invalid
signal
Product: glibc
Version: 2.3.2
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: gotom at debian dot or dot jp
ReportedBy: alan dot johnston at gd-ais dot com
CC: glibc-bugs at sources dot redhat dot com
GCC host triplet: Linux Gentoo 2.6.3-rc3
GCC target triplet: Same as host
http://sources.redhat.com/bugzilla/show_bug.cgi?id=184
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.