http://bugs.freedesktop.org/show_bug.cgi?id=27144
--- Comment #1 from Chris Rankin <ranki...@googlemail.com> 2010-03-18 16:51:10
PST ---
I don't understand the "why" on this one, just that the SIGSEGV happens within
the following WRITE_DEPTH macro:
#define WRITE_DEPTH( _x, _y, d ) \
do { \
GLuint *_ptr = (GLuint*)r600_ptr_depth( rrb, _x + x_off, _y + y_off );
\
GLuint tmp = *_ptr; \
tmp &= 0xff000000; \
tmp |= ((d) & 0x00ffffff); \
*_ptr = tmp; \
_ptr = (GLuint*)r600_ptr_stencil(rrb, _x + x_off, _y + y_off);
\
tmp = *_ptr; \
tmp &= 0xffffff00; \
tmp |= ((d) >> 24) & 0xff; \
*_ptr = tmp; \
} while (0)
The exact location seems to be the second line, where the contents of _ptr are
assigned to GLuint tmp. In my particular example, _x = 640, _y = 971 and d = 0
when it explodes.
It might be worth noting that this is an x86_64 machine, although it's
definitely SIGSEGV and not SIGBUS.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
