Bug 560260 - [abrt] crash in evince-2.28.1-5.fc12
Summary: [abrt] crash in evince-2.28.1-5.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:68d8e79b5ee62958074811589ea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-30 16:50 UTC by Robert Johnson
Modified: 2010-02-24 11:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-24 11:25:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.30 KB, text/plain)
2010-01-30 16:50 UTC, Robert Johnson
no flags Details

Description Robert Johnson 2010-01-30 16:50:24 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: evince file:///tmp/install-2.pdf
comment: This appears to have happened while I was installing updates to bring my new Fedora Core 12 install up to date.
component: evince
executable: /usr/bin/evince
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: evince-2.28.1-5.fc12
rating: 0
reason: Process was terminated by signal 6
release: Fedora release 12 (Constantine)

backtrace
-----
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/evince.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/evince.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/evince.debug
[New Thread 2299]
warning: section .gnu.liblist not found in /usr/lib/debug/usr/bin/evince.debug
warning: section .gnu.conflict not found in /usr/lib/debug/usr/bin/evince.debug
warning: section .dynbss not found in /usr/lib/debug/usr/bin/evince.debug
Cannot access memory at address 0x4b705a4

Thread 2 (Thread 2299):
#0  0x00975416 in ?? ()
No symbol table info available.
#1  0x007f6c45 in ?? ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Thread 1 (Thread 2298):
#0  0x00975416 in ?? ()
No symbol table info available.
#1  0x0066da81 in ?? ()
No symbol table info available.
#2  0x007b3ff4 in ?? ()
No symbol table info available.
#3  0xbfb3def8 in ?? ()
No symbol table info available.
#4  0xbfb3df00 in ?? ()
No symbol table info available.
#5  0x0066f34a in ?? ()
No symbol table info available.
#6  0x00000006 in ?? ()
No symbol table info available.
#7  0xbfb3de78 in ?? ()
No symbol table info available.
#8  0x00000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x4b705a4
No symbol "__abort_msg" in current context.

Comment 1 Robert Johnson 2010-01-30 16:50:26 UTC
Created attachment 387753 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-24 11:25:00 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains unusable backtrace. Sorry for the inconvenience.

Closing as INSUFFICIENT_DATA.


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