Bug 562309 - [abrt] crash in wine-core-1.1.36-1.fc12
Summary: [abrt] crash in wine-core-1.1.36-1.fc12
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wine (Show other bugs)
(Show other bugs)
Version: 12
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:510fcd812815fb341f27573800c...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-05 21:29 UTC by don.t-afraid
Modified: 2010-02-23 13:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-02-23 13:59:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (1.54 KB, text/plain)
2010-02-05 21:29 UTC, don.t-afraid
no flags Details

Description don.t-afraid 2010-02-05 21:29:50 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: 'Z:\\Z:\h\\Z:\home\\Z:\ho Z: Z:\home\\\Z:\home' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
component: wine
executable: /usr/bin/wine-preloader
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: wine-core-1.1.36-1.fc12
rating: 0
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
[New Thread 15389]
Failed to read a valid object file image from memory.
Core was generated by `Z:\home\Mathieu\World Of Warcraft\Wow.exe                                     '.
Program terminated with signal 11, Segmentation fault.
#0  0x78f361d2 in ?? ()

Thread 2 (Thread 15389):
#0  0x68000832 in ?? ()
No symbol table info available.
#1  0x6a0d43d6 in ?? ()
No symbol table info available.
#2  0xffffffff in ?? ()
No symbol table info available.
#3  0x00000001 in ?? ()
No symbol table info available.
#4  0x690057c8 in ?? ()
No symbol table info available.
#5  0x7e030b28 in ?? ()
No symbol table info available.
#6  0x68fef670 in ?? ()
No symbol table info available.
#7  0x7dfb51a8 in ?? ()
No symbol table info available.
#8  0x68fef6b3 in ?? ()
No symbol table info available.
#9  0x7e300498 in ?? ()
No symbol table info available.
#10 0x00000001 in ?? ()
No symbol table info available.
#11 0xffffffff in ?? ()
No symbol table info available.
#12 0x00000077 in ?? ()
No symbol table info available.
#13 0x0000007c in ?? ()
No symbol table info available.
#14 0x0000005b in ?? ()
No symbol table info available.
#15 0x00000038 in ?? ()
No symbol table info available.
#16 0x00000004 in ?? ()
No symbol table info available.
#17 0x00000000 in ?? ()
No symbol table info available.

Thread 1 (Thread 15387):
#0  0x78f361d2 in ?? ()
No symbol table info available.
#1  0x00000000 in ?? ()
No symbol table info available.
No shared libraries loaded at this time.
No symbol "__abort_msg" in current context.

Comment 1 don.t-afraid 2010-02-05 21:29:53 UTC
Created attachment 389202 [details]
File: backtrace

Comment 2 Karel Klíč 2010-02-23 13:59:52 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.