Bug 41579 - R300 Segfaults when using mupen64plus
Summary: R300 Segfaults when using mupen64plus
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r300 (show other bugs)
Version: 7.11
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-07 17:52 UTC by krthurow
Modified: 2012-12-05 16:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Backtrace from r300 segfault when running mupen64plus. (1.97 KB, text/plain)
2011-10-07 17:52 UTC, krthurow
Details

Description krthurow 2011-10-07 17:52:17 UTC
Created attachment 52103 [details]
Backtrace from r300 segfault when running mupen64plus.

When starting up the emulator mupen64plus with a ROM, it crashes before loading the ROM, showing a segfault. Video card is a Mobility Radeon X1700.

Using gdb I traced the segfault back to r300_dri.so
The issues seems to be at line 864 of src/gallium/drivers/r300/r300_emit.c 'buf' is getting set to 0 instead of a proper address.

My backtrace is attached.
Comment 1 Michel Dänzer 2011-10-10 04:30:23 UTC
Does this still happen with current Git?
Comment 2 krthurow 2011-10-11 12:19:20 UTC
(In reply to comment #1)
> Does this still happen with current Git?

Just tested current Git, and it seems to be working.
Comment 3 Michel Dänzer 2011-10-12 02:59:21 UTC
(In reply to comment #2)
> Just tested current Git, and it seems to be working.

Great. If it's still broken with the current 7.11 branch, and you can isolate the change that fixed it, maybe we can backport it.
Comment 4 Marek Olšák 2011-11-07 12:03:14 UTC
Type on master:
git log origin/7.11..origin/master -- src/mesa/state_tracker/st_draw.c

(assuming origin is the main mesa repo)

I am 99.9% sure one of those commits fixes it. :) Please try to find the fix by guess. There are only 7 of them.

I don't have r300 or r500 in my machine right now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.