Bug 602987 – [abrt] coreutils-8.4-8.el6: __nanosleep_nocancel: Process /bin/sleep was killed by signal 6 (SIGABRT)

Bug 602987 - [abrt] coreutils-8.4-8.el6: __nanosleep_nocancel: Process /bin/sleep was killed by signal 6 (SIGABRT)

Summary:	[abrt] coreutils-8.4-8.el6: __nanosleep_nocancel: Process /bin/sleep was kill...

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	coreutils (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Ondrej Vasik
QA Contact:	qe-baseos-daemons
Docs Contact:

URL:
Whiteboard:	abrt_hash:ac3956ed41a5ea095a111949f56...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-06-11 03:58 EDT by Michal Nowak
Modified:	2013-03-07 21:10 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-06-11 03:58:51 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
File: backtrace (2.36 KB, text/plain) 2010-06-11 03:58 EDT, Michal Nowak	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michal Nowak 2010-06-11 03:58:26 EDT

abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: sleep 300
component: coreutils
crash_function: __nanosleep_nocancel
executable: /bin/sleep
global_uuid: ac3956ed41a5ea095a111949f5656cf3fc6935d6
kernel: 2.6.32-33.el6.x86_64
package: coreutils-8.4-8.el6
rating: 4
reason: Process /bin/sleep was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
time: 1276242819
uid: 500

Comment 1 Michal Nowak 2010-06-11 03:58:28 EDT

Created attachment 423170 [details]
File: backtrace

Comment 2 Michal Nowak 2010-06-11 03:58:51 EDT

Sorry, just a test.

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