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
Created attachment 397643 [details] File: backtrace
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 ?
How to reproduce ----- 1. try to do something on a file that is prohibitted (by access control). 2. 3.
(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).
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 ***