Bug 561755 - [abrt] crash in totem-mozplugin-2.28.3-1.fc12
Summary: [abrt] crash in totem-mozplugin-2.28.3-1.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: totem
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b6bf91cc9a2da3701a079d9c316...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-04 08:24 UTC by sunny
Modified: 2010-02-23 14:42 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (1.60 KB, text/plain)
2010-02-04 08:24 UTC, sunny
no flags Details

Description sunny 2010-02-04 08:24:07 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: /usr/libexec/totem-plugin-viewer --plugin-type gmp --user-agent Windows-Media-Player/10.00.00.4019 --mimetype video/x-msvideo --statusbar
component: totem
executable: /usr/libexec/totem-plugin-viewer
kernel: 2.6.31.6-145.fc12.i686.PAE
package: totem-mozplugin-2.28.3-1.fc12
rating: 0
reason: Process was terminated by signal 6
release: Fedora release 12 (Constantine)

backtrace
-----
warning: the debug information found in "/usr/lib/debug//usr/libexec/totem-plugin-viewer.debug" does not match "/usr/libexec/totem-plugin-viewer" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug/usr/libexec/totem-plugin-viewer.debug" does not match "/usr/libexec/totem-plugin-viewer" (CRC mismatch).

warning: core file may not match specified executable file.
[New Thread 2058]
[New Thread 2057]
Cannot access memory at address 0x321d

Thread 3 (Thread 2057):
#0  0x001df416 in ?? ()
No symbol table info available.
#1  0x0080df72 in ?? ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Thread 2 (Thread 2058):
#0  0x001df416 in ?? ()
No symbol table info available.
#1  0x0080df72 in ?? ()
No symbol table info available.
#2  0x00000000 in ?? ()
No symbol table info available.

Thread 1 (Thread 2001):
#0  0x001df416 in ?? ()
No symbol table info available.
#1  0x00684a81 in ?? ()
No symbol table info available.
#2  0x007caff4 in ?? ()
No symbol table info available.
#3  0xbfdaacb0 in ?? ()
No symbol table info available.
#4  0xbfdaacb8 in ?? ()
No symbol table info available.
#5  0x0068634a in ?? ()
No symbol table info available.
#6  0x00000006 in ?? ()
No symbol table info available.
#7  0xbfdaac30 in ?? ()
No symbol table info available.
#8  0x00000000 in ?? ()
No symbol table info available.
Cannot access memory at address 0x321d
No symbol table is loaded.  Use the "file" command.
Debuginfo absent: 4835533114572c59533f43f6a021678b5e888d08
Debuginfo absent: d2e3da5b8ad31a3aa3dcc32e4ae1de55e98d87fd
Debuginfo absent: fa44d89f8e5cf4e44125551f3e5b271cb70e69e9

Comment 1 sunny 2010-02-04 08:24:10 UTC
Created attachment 388737 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-23 14:42:15 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.