I found a similar RH bugfix[1], not upstream[2]. Both backtrace from what I have in Ubuntu[3] and RH bug[4] correlate.
ksh could terminate unexpectedly with a segfault after it received the SIGCHLD signal. See (sig=17) at frame 1 in job_reap. [1] https://access.redhat.com/solutions/1253243 [2] - https://github.com/att/ast [3] (gdb) bt (gdb) bt #0 job_chksave (pid=pid@entry=19003) at /build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:1948 #1 0x00000000004282ab in job_reap (sig=17) at /build/ksh-6IEHIC/ksh-93u+20120801/src/cmd/ksh93/sh/jobs.c:428 #2 <signal handler called> [4] - (gdb) bt #0 job_chksave (pid=5066) at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/jobs.c:1949 #1 0x0000000000429240 in job_reap (sig=17) at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/jobs.c:428 #2 <signal handler called> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697501 Title: ksh segfault on job_chksave () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksh/+bug/1697501/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
