From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26259] New: Wine bloodlines crashes on "new game" on a Radeon Mobility X700 (PCIE)
Date: Tue, 26 Jan 2010 15:50:41 -0800 (PST) [thread overview]
Message-ID: <bug-26259-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26259
Summary: Wine bloodlines crashes on "new game" on a Radeon
Mobility X700 (PCIE)
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: i30817@gmail.com
>From here : http://bugs.winehq.org/show_bug.cgi?id=21493
Wine-dbg>info process
pid threads parent executable (all id:s are in hex)
0000000e 4 0000000a 'services.exe'
00000011 4 0000000e 'winedevice.exe'
00000019 3 0000000e 'winedevice.exe'
00000034 6 00000000 'vampire.exe'
00000038 1 00000034 'explorer.exe'
0000003c 2 00000034 '~e5.0001'
Wine-dbg>attach 0x34
0x68000832 GLIBC_2+0x832 in ld-linux.so.2: ret
Wine-dbg>set $BreakOnFirstChance=0
Wine-dbg>cont
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x4d991190).
Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
EIP:4d991190 ESP:0032d9f4 EBP:0032da3c EFLAGS:00210202( R- -- I - - - )
EAX:00000000 EBX:4dbb2ff4 ECX:00000001 EDX:7d8f1740
ESI:00000000 EDI:7d8f1740
Stack dump:
0x0032d9f4: 7c3d8a98 7c367ca0 0032da3c 4d991e81
0x0032da04: 7ca69268 00000000 00000000 00000000
0x0032da14: 00000000 7c36690c 0000000c 4d973d81
0x0032da24: 7d8f1710 001741a8 4d99115b 4dbb2ff4
0x0032da34: 7c3c3cf0 00000001 0032daec 4d974fc7
0x0032da44: 7d8f1740 00000000 00000000 00000001
Backtrace:
=>0 0x4d991190 radeonEmitVec16+0x40() in r300_dri.so (0x0032da3c)
1 0x4d974fc7 in r300_dri.so (+0x2cfc7) (0x0032daec)
2 0x4da23e66 in r300_dri.so (+0xdbe66) (0x0032db5c)
3 0x4da23fee in r300_dri.so (+0xdbfee) (0x0032db9c)
4 0x4da1b1ce in r300_dri.so (+0xd31ce) (0x0032dbbc)
5 0x20348d14 in wined3d (+0x68d14) (0x0032df6c)
6 0x2031e251 in wined3d (+0x3e251) (0x0032dfbc)
7 0x3bf4b516 in d3d9 (+0xb516) (0x0032e01c)
8 0x2a01203f in shaderapidx9 (+0x1203f) (0x2a068570)
9 0x00490105 (0x2a0527f0)
10 0x2a012580 in shaderapidx9 (+0x12580) (0x2a012470)
0x4d991190 radeonEmitVec16+0x40 in r300_dri.so: movl 0x0(%esi),%edx
Wine-dbg>
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
next reply other threads:[~2010-01-26 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 23:50 bugzilla-daemon [this message]
2010-01-27 14:46 ` [Bug 26259] Wine bloodlines crashes on "new game" on a Radeon Mobility X700 (PCIE) bugzilla-daemon
2010-01-27 14:48 ` bugzilla-daemon
2010-01-27 15:39 ` bugzilla-daemon
2010-01-27 16:35 ` bugzilla-daemon
2010-01-27 16:52 ` bugzilla-daemon
2010-03-11 21:46 ` bugzilla-daemon
2014-07-07 16:43 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26259-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.