All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30131] Command & Conquer 3 crashes with r300g
Date: Thu, 23 Dec 2010 12:40:36 -0800 (PST)	[thread overview]
Message-ID: <20101223204036.F205B13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-30131-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=30131

--- Comment #10 from Martin Stolpe <martinstolpe@gmail.com> 2010-12-23 12:40:36 PST ---
(In reply to comment #9)
> Then you are most probably using direct rendering. Could you possibly obtain a
> backtrace (i.e. call stack) of the crash?

I've tried to switch on wine_d3d, x11drv, x11settings, xrandr, xrender and
xvidmode debug channels in wine, but the resulting log file doesn't seem to
give any hints about the error (if you're interested I can upload the log
file).

Are there any other debug settings which I can turn on, which could help you
identifying the cause of the crash?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-12-23 20:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11  8:07 [Bug 30131] New: Command & Conquer 3 crashes with r300g bugzilla-daemon
2010-09-11 13:30 ` [Bug 30131] " bugzilla-daemon
2010-09-11 16:06 ` bugzilla-daemon
2010-09-12 22:29 ` bugzilla-daemon
2010-09-13  7:35 ` bugzilla-daemon
2010-09-13  7:57 ` bugzilla-daemon
2010-12-17 12:56 ` bugzilla-daemon
2010-12-22 20:47 ` bugzilla-daemon
2010-12-22 21:21 ` bugzilla-daemon
2010-12-23 12:25 ` bugzilla-daemon
2010-12-23 12:37 ` bugzilla-daemon
2010-12-23 20:40 ` bugzilla-daemon [this message]
2010-12-23 21:26 ` bugzilla-daemon
2011-02-11  1:43 ` bugzilla-daemon
2011-02-11 16:42 ` bugzilla-daemon
2011-02-11 17:33 ` bugzilla-daemon
2011-02-11 19:15 ` bugzilla-daemon
2011-02-11 20:57 ` bugzilla-daemon
2011-02-12  8:55 ` bugzilla-daemon
2011-02-13 18:03 ` bugzilla-daemon
2011-02-13 20:21 ` bugzilla-daemon
2011-02-16 22:38 ` bugzilla-daemon
2011-02-17  0:11 ` bugzilla-daemon
2011-02-17  1:42 ` bugzilla-daemon
2011-02-17 19:57 ` 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=20101223204036.F205B13004E@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 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.