This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: Signal handling broken with -lpthread
Andreas Jaeger <aj@arthur.rhein-neckar.de> writes:
|> >>>>> Akos Szalkai writes:
|>
|> >> Description:
|> > It seems that any program using the sigaction function
|> > segfaults if it is linked with -lpthread. The segmentation
|> > fault does not occur with glibc-2.0.94 or if -lpthread is not
|> > used.
|> >> How-To-Repeat:
|> > Consider the following trivial program:
|> > -----cut here-----
|> > #include <signal.h>
|>
|> > int
|> > main (void)
|> > {
|> > struct sigaction old_action;
|>
|> > sigaction (SIGINT, 0, &old_action);
|>
|> > return 0;
|> > }
|> > -----cut here-----
|>
|> > Linking it with -lpthread, it causes a segfault when run. The
|> > segfault does not occur if it is not linked with -lpthread.
|>
|> I can't reproduce this with the current development version of glibc
|> 2.1 (2.0.95 plus lot's of patches). I see the following explanations:
[...]
|> - this has been fixed already
This describes the situation accurately:
1998-08-08 11:18 H.J. Lu <hjl@gnu.org>
* signals.c (sigaction): Handle NULL argument.
Andreas.