Re: Issue with Bash

[Chet Ramey]

On 7/31/20 3:25 AM, Rishita Saha16 wrote:
> Hi All,
>  
> We have been able to recreate a scenario where bash dumps core immediately
> on issuing a SIGHUP to the parent process (kill -1 <parent-pid>). On
> debugging, the core so generated shows exactly the same stack trace as we
> had seen with the previous core. Below is the truss output of bash process
> when the parent process of bash (ksh, in this case) gets a SIGHUP:

I'm trying to figure out the scenario here. An interactive bash, which is
the child of an interactive ksh, runs `kill -1 $PPID'. The parent ksh
apparently closes the controlling terminal (?), then resends the SIGHUP
to its children (bash) before exiting.

The interactive bash catches SIGHUP in readline, attempts to clean up the
terminal by restoring the original settings, and gets SIGHUP (?), even
though SIGHUP isn't one of the signals that's supposed to be sent when you
use tcsetattr.

I'd love to know what's happening to the controlling terminal here,
assuming the scenario I've outlined is what's happening.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/