From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35051] [r600g, Wine, Counter Strike Source] Crashes at Startup
Date: Tue, 8 Mar 2011 05:02:20 -0800 (PST) [thread overview]
Message-ID: <20110308130220.B417F13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-35051-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=35051
--- Comment #1 from Henri Verbeet <hverbeet@gmail.com> 2011-03-08 05:02:19 PST ---
I'm able to at least run the CS:S stress tests with current git versions of
Wine and r600g on Evergreen, although rendering correctness and performance
still have some way to go. The "Inconsistency detected by ld.so: ..." line in
the log looks suspicious, although it's unclear to me if it's related to the
cause of the crash. Normally when source engine games crash they write a
minidump in "dumps" in your Steam directory, you can open those with winedbg to
get a backtrace. The dbghelp FIXME and ld.so message make me suspect it might
have failed to produce a usable minidump this time though.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-03-08 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 4:39 [Bug 35051] New: [r600g, Wine, Counter Strike Source] Crashes at Startup bugzilla-daemon
2011-03-08 13:02 ` bugzilla-daemon [this message]
2011-03-08 15:06 ` [Bug 35051] " bugzilla-daemon
2011-03-08 19:13 ` [Bug 35051] [RADEON:KMS:R600G] wine Counter Strike Source " bugzilla-daemon
2011-03-08 20:56 ` bugzilla-daemon
2011-03-09 9:56 ` bugzilla-daemon
2011-03-09 21:20 ` bugzilla-daemon
2011-03-10 8:37 ` bugzilla-daemon
2011-03-12 1:59 ` bugzilla-daemon
2011-05-15 21:10 ` bugzilla-daemon
2011-05-15 21:13 ` bugzilla-daemon
2011-05-16 12:54 ` bugzilla-daemon
2011-05-16 16:15 ` bugzilla-daemon
2011-06-23 0:47 ` bugzilla-daemon
2011-06-23 9:47 ` 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=20110308130220.B417F13004E@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).