bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On solaris, a SIGINT sent to a child process of Korn Shell kills the


From: Stefano Lattarini
Subject: Re: On solaris, a SIGINT sent to a child process of Korn Shell kills the shell itself
Date: Mon, 12 Sep 2011 23:25:02 +0200
User-agent: KMail/1.13.7 (Linux/2.6.30-2-686; KDE/4.6.5; i686; ; )

On Monday 12 September 2011, Stefano Lattarini wrote:
> On Monday 12 September 2011, Stefano Lattarini wrote:
> >
> > The "default" Korn Shell on Debian GNU/Linux (package `ksh', version
> > `93u-1') seems to exhibit the same issue.
> >  
> > And if I'm not reading the strace output wrong, this is due to the fact
> > that the Debian korn shell is apparently killing itself (yikes!) with the
> > same signal that killed the child process:
>
> It's better on Solaris: its /bin/ksh (and /usr/xpg4/bin/sh) "only" exit
> with status 130 [*] if a child is terminated by a SIGINT; so the signal is
> not "recursively propagated".
> 
> [*] Well, it still executes the trap associated with SIGINT, but probably
>     does so through special-cased code, without passing through real `kill'
>     system calls.  I guess.
> 
These might also be useful to better understand the issue in question:
 
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2009-February/004121.html>
 <http://www.cons.org/cracauer/sigint.html>
In particular, the second one hints how the ksh behaviour might be desirable
sometimes.  Still, other times it's just a PITA, so I'd love to have an option
to disable it.  Oh well, now that I've understood the problem, working around
it in the automake testsuite shouldn't be too difficult anyway.

Regards,
  Stefano


reply via email to

[Prev in Thread] Current Thread [Next in Thread]