I believe I found a bug in /arch/ppc/kernel/signal.c
barrow_dj at yahoo.com
Wed Feb 24 23:45:06 EST 1999
setjmp in glibc2 compiles to sigsetjmp(env,0) i.e. it doesn't save the
The sigsetjmp gets rid of the signal being blocked issue ( the main
symptom ), there still can be outstanding signals on the user stack
being trashed though.
---Lauro Whately <whately at cos.ufrj.br> wrote:
> > On Mon, Feb 22, 1999, D.J. Barrow <barrow_dj at yahoo.com> wrote:
> > The bug manifested itself in tftp, when longjmp'ing out
> > of the signal handler on timeouts.
> > Resulting in....
> > a )sys_sigreturn not get called
> > b) signals queued & trampoline stuff on the user stack being
> > c) SIGALRM being blocked forever.
> Have you tried the sigsetjmp/siglongjmp ?
> I've met a similar problem a month ago and found that POSIX.1 does not
> specify the effect of setjmp and longjmp on signal masks (SVR4 does
> and restore the signal mask under setjmp/longjmp, however 4.3 BSD
> restore the signal mask) Instead, two new functions sigsetjmp and
> are defined by POSIX.1
> Those new ones are working ok with linux 2.1.x releases (I've been
> with linuxppc 2.1.112)
> It seems that the behavior of sigsetjmp/siglongjmp was changed to
> specification around the release 2.1.112.
> Lauro Whately
> Parallel Computing Lab. / COPPE
> Federal University of Rio de Janeiro
> "A distributed system is one on which I cannot get any work done,
> machine I have never heard of has crashed." -- Leslie Lamport
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request at lists.linuxppc.org ]]
More information about the Linuxppc-dev