Created attachment 490098 [details] small part of a .shrc used to trigger the 'Memory fault' in ksh Description of problem: ksh gives a 'Memory fault' instead of the expected output when running a script Version-Release number of selected component (if applicable): ksh-20110208-3.fc14.i686 How reproducible: Happens every time Steps to Reproduce: 1. Download http://www.kornshell.com/examples/shprof and the attached test.sh 2. (to get shprof working, replace "file=$(whence "$1")" with "file=$1" on line 47) 3. run: ksh shprof $PWD/test.sh 4. should give 'Memory fault' and "[109792.538192] ksh[10679]: segfault at 1e00092b ip 0811c530 sp bf9b8a20 error 4 in ksh[8048000+14e000]" in dmesg Actual results: Memory fault Expected results: 7838807 1: # $FreeBSD: src/share/skel/dot.shrc,v 1.3.36.1.6.1 2010/12/21 17:09:25 kensmith Exp $ 1 18: :set -o emacs Additional info: ksh -c 'echo ${.sh.version}' -> Version JM 93u 2011-02-08
reproducible with ksh-20110208-3.fc14.i686, seems to work fine with 64bit version
ksh-20110505-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ksh-20110505-1.fc14
Package ksh-20110505-1.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ksh-20110505-1.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/ksh-20110505-1.fc14 then log in and leave karma (feedback).
ksh-20110505-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/ksh-20110505-2.fc15
ksh-20110505-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ksh-20110505-2.fc14
ksh-20110505-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
ksh-20110505-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.