Re: SIGALRM and default handler

Il 15/09/2014 19:46, Holger Hans Peter Freyther ha scritto:
> Dear Paolo,
> 
> I am running an image with gst-remote and it appears to be terminated
> with SIGALRM due having a default handler. I thought it might have
> been introduced by looking with GDB but it happens with strace (sure
> both gdb and strace use ptrace).
> 
> #0  *__GI___sigaction (sig=14, act=0xbfe20de4, oact=0xbfe20d58) at ../nptl/sigaction.c:37
> #1  0xb768539a in _gst_set_signal_handler (signum=14, handlerFunc=0)
>     at sysdep/posix/signals.c:130
> #2  0xb76b2daf in signal_handler (sig=14) at events.c:82
> #3  <signal handler called>
> #4  0xb76ff424 in __kernel_vsyscall ()
> #5  0xb74f5b57 in do_sigsuspend (set=0xb760dff4)
>     at ../sysdeps/unix/sysv/linux/sigsuspend.c:63
> 
> 
> So when handlerFunc=0 we seem to revert SIG_DEF for SIGALRM?

Yes, I think as soon as the Smalltalk image decides to handle a signal,
the reset action should be SIG_IGN, not SIG_DFL.

Paolo