Bug 921821 - [abrt] ksh-20120801-6.fc17: job_chksave: Process /usr/bin/ksh was killed by signal 11 (SIGSEGV)
Summary: [abrt] ksh-20120801-6.fc17: job_chksave: Process /usr/bin/ksh was killed by s...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ksh
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:692eb2ad6bf413fdcf073360fbf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-15 02:41 UTC by Daniel
Modified: 2013-08-01 07:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 05:03:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.38 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: cgroup (132 bytes, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: core_backtrace (2.03 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: dso_list (552 bytes, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: environ (2.52 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: maps (2.67 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: open_fds (102 bytes, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: proc_pid_status (920 bytes, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: smolt_data (2.44 KB, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details
File: var_log_messages (284 bytes, text/plain)
2013-03-15 02:42 UTC, Daniel
no flags Details

Description Daniel 2013-03-15 02:41:58 UTC
Version-Release number of selected component:
ksh-20120801-6.fc17

Additional info:
backtrace_rating: 4
cmdline:        /bin/ksh /opt/ibm/db2/V9.7/itma/bin/cinfo -R
crash_function: job_chksave
executable:     /usr/bin/ksh
kernel:         3.7.9-104.fc17.x86_64
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 job_chksave at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/jobs.c:1948
 #1 job_reap at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/jobs.c:428
 #3 job_subsave at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/jobs.c:1988
 #4 sh_subshell at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/subshell.c:498
 #5 comsubst at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/macro.c:2135
 #6 varsub at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/macro.c:1168
 #7 copyto at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/macro.c:633
 #8 sh_mactrim at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/macro.c:183
 #9 nv_setlist at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/name.c:339
 #10 sh_exec at /usr/src/debug/ksh-20120801/src/cmd/ksh93/sh/xec.c:1210

Comment 1 Daniel 2013-03-15 02:42:02 UTC
Created attachment 710357 [details]
File: backtrace

Comment 2 Daniel 2013-03-15 02:42:04 UTC
Created attachment 710358 [details]
File: cgroup

Comment 3 Daniel 2013-03-15 02:42:05 UTC
Created attachment 710359 [details]
File: core_backtrace

Comment 4 Daniel 2013-03-15 02:42:07 UTC
Created attachment 710360 [details]
File: dso_list

Comment 5 Daniel 2013-03-15 02:42:09 UTC
Created attachment 710361 [details]
File: environ

Comment 6 Daniel 2013-03-15 02:42:11 UTC
Created attachment 710362 [details]
File: limits

Comment 7 Daniel 2013-03-15 02:42:14 UTC
Created attachment 710363 [details]
File: maps

Comment 8 Daniel 2013-03-15 02:42:16 UTC
Created attachment 710364 [details]
File: open_fds

Comment 9 Daniel 2013-03-15 02:42:18 UTC
Created attachment 710365 [details]
File: proc_pid_status

Comment 10 Daniel 2013-03-15 02:42:20 UTC
Created attachment 710366 [details]
File: smolt_data

Comment 11 Daniel 2013-03-15 02:42:22 UTC
Created attachment 710367 [details]
File: var_log_messages

Comment 12 Michal Hlavinka 2013-03-29 11:18:10 UTC
Thanks for reporting this. Are you able to reproduce this bug? If so, could you provide steps required to reproduce it?
thanks

Comment 13 Daniel 2013-04-01 02:12:05 UTC
(In reply to comment #12)
> Thanks for reporting this. Are you able to reproduce this bug? If so, could
> you provide steps required to reproduce it?
> thanks

Sorry, I even do not know how this crash happened.
The abrt tool reported this crash automatically for me.

Comment 14 Fedora End Of Life 2013-07-04 00:59:29 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2013-08-01 05:03:32 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.