Bug 21688 - [radeon-rewrite] blender crashes in radeon_update_renderbuffers
Summary: [radeon-rewrite] blender crashes in radeon_update_renderbuffers
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R100 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-11 11:54 UTC by Tormod Volden
Modified: 2009-05-12 05:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
full backtrace of blender (1.58 KB, text/plain)
2009-05-11 11:54 UTC, Tormod Volden
Details
Xorg.0.log (44.87 KB, text/plain)
2009-05-11 11:56 UTC, Tormod Volden
Details
avoid segfault in radeon_update_renderbuffers() if using DRI1 (1.77 KB, patch)
2009-05-12 00:37 UTC, Tormod Volden
Details | Splinter Review

Description Tormod Volden 2009-05-11 11:54:52 UTC
Created attachment 25746 [details]
full backtrace of blender

Blender crashes at startup, with today's radeon-rewrite:

#0  0xb61ca2e0 in radeon_update_renderbuffers (context=0x8e47338, 
    drawable=0x91e8618) at radeon_common_context.c:447
#1  0xb61cce1d in radeonDrawBuffer (ctx=0x8e9f4f0, mode=1028)
    at radeon_common.c:811
#2  0xb61dfbf2 in _mesa_DrawBuffer (buffer=1028) at main/buffers.c:267
#3  0x0819c870 in splash ()
#4  0x081a0fcd in screenmain ()
#5  0x08190b95 in main ()
Comment 1 Tormod Volden 2009-05-11 11:56:05 UTC
Created attachment 25747 [details]
Xorg.0.log
Comment 2 Joel Bosveld 2009-05-11 18:15:54 UTC
If this is with dri1, something like this: http://cgit.freedesktop.org/mesa/mesa/commit/?h=radeon-rewrite&id=43d9020ff1e975e7f4f9480d9ef24f0b9fb2141f
is probably needed.
Comment 3 Tormod Volden 2009-05-12 00:37:55 UTC
Created attachment 25786 [details] [review]
avoid segfault in radeon_update_renderbuffers() if using DRI1

Thanks, yes, that works.
Comment 4 Jerome Glisse 2009-05-12 05:53:10 UTC
Patch pushed thanks.


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.