Bug 570293

Summary: [abrt] crash in ksh-20100202-1.fc12: Process /bin/ksh was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jeff Frontz <jhfrontz>
Component: kshAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jeff.frontz, mhlavink
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:89dbe2528138a21bb244f9e585ceb354b93b7a17
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-01 10:50:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Jeff Frontz 2010-03-03 19:34:43 UTC 
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: -ksh
comment: unknoiwn
component: ksh
executable: /bin/ksh
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: ksh-20100202-1.fc12
rating: 4
reason: Process /bin/ksh was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
How to reproduce: unknown
Comment 1 Jeff Frontz 2010-03-03 19:34:46 UTC 
Created attachment 397643 [details]
File: backtrace
Comment 2 Michal Hlavinka 2010-03-04 08:44:26 UTC 
thanks for reporting this. Do you know what were you doing before it crashed? It seems it's related to content of PATH variable

what output gives you following command:

echo $PATH

?
Comment 3 Jeff Frontz 2010-03-26 21:26:42 UTC 

How to reproduce
-----
1. try to do something on a file that is prohibitted (by access control).
2.
3.
Comment 4 Jeff Frontz 2010-03-26 22:51:09 UTC 
(In reply to comment #2)
> thanks for reporting this. Do you know what were you doing before it crashed?
> It seems it's related to content of PATH variable
> 
> what output gives you following command:
> 
> echo $PATH
> 
> ?    

Here's my PATH variable:

$ echo $PATH
/home/jhf/bin:/etc:/usr/lbin:/usr/local/bin:/usr/local/etc:/usr/sbin:/usr/ccs/bin:/home/jhf/bin:/etc:/usr/lbin:/usr/local/bin:/usr/local/etc:/usr/sbin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/openwin/bin:/usr/openwin/bin

(it's from my generic .profile that I [have] use[d] on various OSs, so there's lots of crufty stuff in it)

I think most times when this happens, I'm either cd'ing to someplace that I don't have permission for or maybe ls'ing a directory that is unreadable, but I don't know for sure-- I'm often not paying close attention to the screen as I'm typing and don't realize for several seconds that something bad has happened (after which time, my xterm/terminal application has closed).
Comment 5 Michal Hlavinka 2010-04-01 10:50:55 UTC 
this crashed on the same line like the crash in your other bug report, which uses more up-to-date ksh version

*** This bug has been marked as a duplicate of bug 578582 ***