Bug 827202 - Generated a unusable backtrace
Summary: Generated a unusable backtrace
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 21:44 UTC by Carlos Soriano
Modified: 2012-08-09 21:50 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-09 21:50:29 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Carlos Soriano 2012-05-31 21:44:10 UTC 
Description of problem:
When I try to generate a backtrace for a telepathy bug, the backtrace becomes unusable, so I can't file a bug
This is the generated backtrace: http://pastebin.com/sgb3Y3ke

Fedora 17

I also see possible duplicates like #808904, but it didn't happens with the same package.
Comment 1 Carlos Soriano 2012-05-31 22:10:13 UTC 
Also happens with a bug in empathy. This is the backtrace
http://pastebin.com/eZCDRjRS
Comment 2 Carlos Soriano 2012-05-31 22:52:01 UTC 
Also happens with chromium bug. This is the backtrace:
http://pastebin.com/SEYzLhGX
Comment 3 Jiri Moskovcak 2012-06-15 08:48:19 UTC 
Did you use retrace server or local gdb to generate the backtrace?
Comment 4 Carlos Soriano 2012-06-19 23:24:25 UTC 
local dbg, retrace server was not avaiable when I reported the bug.
I think that I can't reproduce the bug again with telephaty, because I didn't get again the bug from telephaty
Comment 5 Jiri Moskovcak 2012-08-09 21:50:29 UTC 
Sometimes the important parts of the used memory gets overwritten and the coredump is unusable. That's something that ABRT nor GDB can fix.
Note You need to log in before you can comment on or make changes to this bug.