Version-Release number of selected component: ksh-20120801-17.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /bin/ksh ./testrun.ksh crash_function: sh_done executable: /usr/bin/ksh kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #1 sh_done at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/fault.c:664 #2 sh_main at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/main.c:354 #4 _start
Created attachment 890564 [details] File: backtrace
Created attachment 890565 [details] File: cgroup
Created attachment 890566 [details] File: core_backtrace
Created attachment 890567 [details] File: dso_list
Created attachment 890568 [details] File: environ
Created attachment 890569 [details] File: limits
Created attachment 890570 [details] File: maps
Created attachment 890571 [details] File: open_fds
Created attachment 890572 [details] File: proc_pid_status
Created attachment 890573 [details] File: var_log_messages
Thanks to reporting this. Do you know how to reproduce it and could you describe the steps how to do so?
All I can really say is that the script that crashed was running a Perl script I was in the midst of debugging (I had prepended "perl -d" to the script invocation). It only did it once, and it did it after I closed the debug session, but I've been running this script in and out of debug mode constantly over the past few days. The text of the ksh script is as follows: #!/bin/ksh ./KnotTab.pl --spm=spmu710314 --echo --strata=security_id --target=returns \ --predictor=maxup --modname=test --spm70 rf_data.csv testrun.csv The Perl script in turn called a binary executable (my employer's proprietary software currently under development), which conceivably could have been a factor as well; but as I said, the ksh script only crashed once. Sorry I couldn't be more help.
OK, thanks for the info.
This is similar to another bug we found. The fix for the other bug should fix this too.
ksh-20120801-19.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ksh-20120801-19.fc19
ksh-20120801-19.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ksh-20120801-19.fc20
Package ksh-20120801-19.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ksh-20120801-19.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-8804/ksh-20120801-19.fc20 then log in and leave karma (feedback).
ksh-20120801-19.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
ksh-20120801-19.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.