On Wed, 2002-06-05 at 19:18, Jens Owen wrote: > While looking at the DRI overhead, I got curious about x11perf results. > Consequently, I tried a run, just to get a baseline, and segfaulted the > server. > > This can be reproduced with: > > x11perf -seg100c2 > > when the DRI is enabled. > > Here is a stack trace from a static server built from the TCL branch. > > Program received signal SIGSEGV, Segmentation fault. > RADEONCPDisableClipping (pScrn=0x85a58c8) at radeon_accel.c:1408 > 1408 OUT_RING_REG(RADEON_SC_BOTTOM_RIGHT, > (RADEON_DEFAULT_SC_RIGHT_MAX > (gdb) bt > #0 RADEONCPDisableClipping (pScrn=0x85a58c8) at radeon_accel.c:1408
Well, the clipping code is certainly broken, not preserving DP_GUI_MASTER_CNTL contents, but it's strange to segfault there. Could it have written beyond the indirect buffer? If so, maybe some CP updates I sent to Kevin would help. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
