On 7/9/20 5:17 AM, Rishita Saha16 wrote:
> Hi All,
>
> We are using Bash 5.0 (64bit built using gcc ) in AIX 7.2 machine .This
> is the spec file for reference -->
> [1]https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/SPECS/bash-5.
> 0-1.spec.
> We are seeing recurring bash core dumps on our servers. Leaving bash
> sessions running on the servers for extended periods of time causes the
> core dump (to recreate it, we left httpd running for about a week and a
> half and encountered the core dump). I am hereby sharing the stack
> trace of the core so generated.
>
> #0 0x0900000000038d0c in __ioctl () from /usr/lib/libc.a(shr_64.o)
> #1 0x09000000000392c8 in ioctl () from /usr/lib/libc.a(shr_64.o)
> #2 0x09000000001c16f0 in tcsetattr () from /usr/lib/libc.a(shr_64.o)
> #3 0x00000001000aec78 in set_tty_settings (tty=0, tiop=0x110013a90
> <_rltty.bss_3_+64>) at rltty.c:466
> #4 0x00000001000aef58 in rl_deprep_terminal () at rltty.c:704
> #5 0x000000010002cf38 in rl_cleanup_after_signal () at signals.c:559
> #6 0x000000010002d500 in _rl_handle_signal (sig=268438344) at
> signals.c:249
Is there any way you can get a better idea of the actual signal delivered?
I suspect it's SIGTTOU, but it would be nice to be sure.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
