Bug 719148

Summary: This bug was cloned from 654519 because 654519 was discovered in product Customer Diagnostics whereas this problem was found in product Red Hat Enterprise Linux 6
Product: Red Hat Enterprise Linux 6 Reporter: Red Hat Case Diagnostics <case-diagnostics>
Component: coreutilsAssignee: Ondrej Vasik <ovasik>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: meyering, prc
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:63c0db54fea86cefc0d744858c2448213f62eb4a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-07 08:29:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 654519    
Bug Blocks:    
Attachments:
Description Flags
File: backtrace none

Description Red Hat Case Diagnostics 2011-07-05 21:40:16 UTC 
+++ This bug was initially created as a clone of Bug 654519 +++

Andreas Testing: 
  Original product: Red Hat Enterprise Linux 6
  Original version: 6.0
  Original component: coreutils
This is a bug generated by abrt

--- Additional comment from biwang onThu Nov 18 05:11:02 EST 2010 ---
Created attachment 461212 [details]
File: backtrace
Comment 2 Red Hat Case Diagnostics 2011-07-05 21:40:51 UTC 
Created attachment 511397 [details]
File: backtrace
Comment 5 RHEL Program Management 2011-07-06 00:58:11 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 Ondrej Vasik 2011-07-07 08:29:29 UTC 
If you intentionally kill sleep command it is expected that it will generate sigabrt report in abrt ... that's not a bug. As I don't see anything wrong in sleep, closing NOTABUG ... btw. this summary is just horrible.
Comment 7 Ondrej Vasik 2011-07-07 08:32:39 UTC 
Btw. these two backtraces do differ - one is sigsegv (signal 11) and one is sigabrt (signal 6) ... anyway - without full backtrace are just useless (and I don't think this is a bug in sleep)