Bug 714403 - [abrt] root-5.28.00d-1.fc14: __libc_message: Process /usr/bin/root.exe was killed by signal 6 (SIGABRT)
Summary: [abrt] root-5.28.00d-1.fc14: __libc_message: Process /usr/bin/root.exe was ki...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: root
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattias Ellert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:24959bfe965726c1edb15dc94a1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-19 01:32 UTC by Calem Hoffman
Modified: 2011-06-26 21:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-26 21:35:21 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (72.31 KB, text/plain)
2011-06-19 01:32 UTC, Calem Hoffman 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Calem Hoffman 2011-06-19 01:32:30 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 74041 bytes
cmdline: root.exe -l
component: root
Attached file: coredump, 43372544 bytes
crash_function: __libc_message
executable: /usr/bin/root.exe
kernel: 2.6.35.13-92.fc14.x86_64
package: root-5.28.00d-1.fc14
rating: 4
reason: Process /usr/bin/root.exe was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1308445959
uid: 500

How to reproduce
-----
1.root.exe -l
2.
3.
Comment 1 Calem Hoffman 2011-06-19 01:32:32 UTC 
Created attachment 505422 [details]
File: backtrace
Comment 2 Mattias Ellert 2011-06-26 02:52:58 UTC 
Can you provide more information about how to reproduce this bug, Like a root macro or sequence of commands that triggers it. I can not reproduce this by simply running "root.exe -l" as the report suggests.
Comment 3 Calem Hoffman 2011-06-26 14:25:33 UTC 
Hello, unfortunately I have no additional information. This bug has not been reproducible. At this point I would say the "bug" was user error. Apologies.
Note You need to log in before you can comment on or make changes to this bug.