From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35051] New: [r600g, Wine, Counter Strike Source] Crashes at Startup
Date: Sat, 5 Mar 2011 20:39:12 -0800 (PST) [thread overview]
Message-ID: <bug-35051-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35051
Summary: [r600g, Wine, Counter Strike Source] Crashes at
Startup
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: bpaterni@gmail.com
Created an attachment (id=44162)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44162)
wine output
I have a similar bug to this one at the winehq bugtracker, but I think it
pertains more to mesa now.
As the title states, counter strike source crashes at start up for me. A full
log of wine's output will be attached.
I think this bug is related to the r600 gallium driver because the game does
load, play, and display with gallium's softpipe driving it, although it is
painfully slow.
Also I believe the critical section of the log is the following:
trace:dbghelp:get_wine_loader_name returning L"wine"
trace:dbghelp:elf_load_file Processing elf file 'L"wine"' at 00000000
trace:dbghelp:elf_load_file Processing elf file 'L".//wine"' at 00000000
trace:dbghelp:elf_load_file Processing elf file 'L"/home/bpaterni/bin/wine"' at
00000000
trace:dbghelp:elf_load_file Processing elf file 'L"/usr/local/bin/wine"' at
00000000
trace:dbghelp:SymFromName (0xffffffff, libwine.so.1!__wine_main_environ,
0xffed654)
trace:dbghelp:SymFromName null process
fixme:dbghelp:elf_search_auxv can't find symbol in module
Inconsistency detected by ld.so: dl-deps.c: 626: _dl_map_object_deps: Assertion
`nlist > 1' failed!
I've looked through wine's source and elf_search_auxv is being called from
MiniDumpWriteDump in dlls/dbghelp/minidump.c which apparently is being called
from within steam/counter strike. Because of this, I'm not sure how to proceed
in debugging since steam/counter strike are both closed. Hopefully someone here
has a clever idea on getting to the bottom of this...
environment:
Linux kernel (git master, linus' tree -- although I have tried drm-next + s3tc,
same result)
Debian unstable/experimental
mesa (git master @ f95892b46a9a6b5d90437998ef9a3babd55e9c7d)
wine (git master)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-03-06 4:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 4:39 bugzilla-daemon [this message]
2011-03-08 13:02 ` [Bug 35051] [r600g, Wine, Counter Strike Source] Crashes at Startup bugzilla-daemon
2011-03-08 15:06 ` 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=bug-35051-502@http.bugs.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).