Bug 729788

Summary: [abrt] ksh-20110505-2.fc14: sfsync: Process /bin/ksh was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael Veksler <mickey.veksler>
Component: kshAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mhlavink
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e94275c029c25531aeb0819f4dd3bab9142f6821
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-19 06:55:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Michael Veksler 2011-08-10 20:03:20 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 21555 bytes
cmdline: /bin/ksh ./AdjustOutputFile /home/veksler/tpa/GPRO.question-marks/gpro/system/P8/regression/output/pstream.tst
component: ksh
Attached file: coredump, 503808 bytes
crash_function: sfsync
executable: /bin/ksh
kernel: 2.6.35.13-92.fc14.x86_64
package: ksh-20110505-2.fc14
rating: 4
reason: Process /bin/ksh was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1313001527
uid: 321

How to reproduce
-----
1. Run my script, which invokes an application that takes 5 CPU minutes
2. Everything seems to have completed correctly, other than the SEGV at the end of the script
Comment 1 Michael Veksler 2011-08-10 20:03:24 UTC 
Created attachment 517683 [details]
File: backtrace
Comment 2 Michal Hlavinka 2011-08-15 14:00:52 UTC 
Thanks for reporting this. Could you provide me the script you are using? I've been looking in the ksh code, but did not find anything useful.

Also, you can test newer ksh version, if you want:

sudo yum update --enablerepo=updates-testing ksh
Comment 3 Michael Veksler 2011-08-30 10:41:50 UTC 
I can't send you the script it is proprietary.
I'll check with a newer KSH.
Comment 4 Michael Veksler 2011-09-18 07:06:32 UTC 
After running for some time, with the updated ksh, I can no longer reproduce this crash.