From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 30131] Command & Conquer 3 crashes with r300g
Date: Thu, 23 Dec 2010 12:40:36 -0800 (PST)
Message-ID: <20101223204036.F205B13004E@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 89E989E814
for ;
Thu, 23 Dec 2010 12:40:37 -0800 (PST)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=30131
--- Comment #10 from Martin Stolpe 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.