Bug 568686

Summary: Abrt report did not contain register status
Product: [Fedora] Fedora Reporter: Lubomir Rintel <lkundrak>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mnowak, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: abrt-1.0.9-1.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-13 01:45:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lubomir Rintel 2010-02-26 11:18:38 UTC
Bug report bug #568680 is not of much use -- I can't tell if the invalid access was a NULL dereference or read of some other unallocated memory.

It would bye really awesome if the report contained output of "info regs" and a disassembly of the code around eip at the time of crash.

Thank you!

Comment 1 Denys Vlasenko 2010-02-26 17:17:03 UTC
Sounds like a good idea. I implemented it in git.

Comment 2 Fedora Update System 2010-04-06 18:54:22 UTC
abrt-1.0.9-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/abrt-1.0.9-1.fc13

Comment 3 Fedora Update System 2010-04-07 20:55:54 UTC
abrt-1.0.9-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update abrt'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/abrt-1.0.9-1.fc13

Comment 4 Fedora Update System 2010-04-13 01:44:04 UTC
abrt-1.0.9-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.