Bug 561015 - [abrt] crash in emacs-1:23.1-14.fc12
Summary: [abrt] crash in emacs-1:23.1-14.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jonathan Underwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:76d719c74be6ded99ec009ba41c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-02 14:05 UTC by Joel James Adamson
Modified: 2010-02-02 14:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-02 14:16:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (465 bytes, text/plain)
2010-02-02 14:05 UTC, Joel James Adamson
no flags Details

Description Joel James Adamson 2010-02-02 14:05:25 UTC
abrt 1.0.4 detected a crash.

architecture: x86_64
cmdline: emacs
component: emacs
executable: /usr/bin/emacs-23.1
kernel: 2.6.31.9-174.fc12.x86_64
package: emacs-1:23.1-14.fc12
rating: 0
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
Cannot access memory at address 0xd

Thread 1 (Thread 3241):
#0  0x0000003f9c6329a7 in ?? ()
No symbol table info available.
#1  0x00000000004dc611 in ?? ()
No symbol table info available.
#2  0x0000003f9d20f0f0 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0xd
No symbol table is loaded.  Use the "file" command.

Comment 1 Joel James Adamson 2010-02-02 14:05:27 UTC
Created attachment 388303 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-02 14:16:09 UTC
Joel, 
the attached backtrace is completely unuseful due to a flaw in ABRT. If you can regenerate the backtrace with debuginfos installed, please report it again. 

Now I am closing it as INSUFFICIENT_DATA.

Thanks for reporting.


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