"Jacob (=Jouk) Jansen" wrote:
>
> Hi all,
>
> When running xlockmore with Mesa3.3 this morning (MET) I get in some of the
> demos this runtime error
> polka-jj) xlock -nice 0 -modelist allgl -inwindow
> X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
> Major opcode of failed request: 70 (X_PolyFillRectangle)
> Resource id in failed request: 0x0
> Serial number of failed request: 5197
> Current serial number in output stream: 5298
> %XLIB-E-ERROREVENT, error event received from server
> %TRACE-E-TRACEBACK, symbolic stack dump follows
> image module routine line rel PC abs PC
> 0 FFFFFFFF80B80480 FFFFFFFF80B80480
> 0 FFFFFFFF80B80670 FFFFFFFF80B80670
> 0 FFFFFFFF80B8392C FFFFFFFF80B8392C
> 0 FFFFFFFF80B7EA18 FFFFFFFF80B7EA18
> 0 FFFFFFFF80B07BD0 FFFFFFFF80B07BD0
> XLOCK XLOCK justDisplay 32864 00000000000032B4 00000000001232B4
> XLOCK XLOCK main 33928 0000000000006068 0000000000126068
> XLOCK XLOCK __main 0 0000000000000070 0000000000120070
> XLOCK 0 000000000022D680 000000000023D680
> 0 FFFFFFFF83A1D3D4 FFFFFFFF83A1D3D4
> polka-jj)
>
> Yesterday's morning (MET) Mesa3.3 did not show this behaviour (I only have
> to change the 2 sharable libraries to get the effect or not)
> Who did change the X-driver?
> Why was it changed?
> What was changed?
> How can this problem be fixed?
Yesterday I checked in a few changes to xmesaP.h, xmesa1.c and xmesa2.c
which fixed some problems with 24bpp rendering and buffer clearing.
Can you get a more detailed stack trace? Setting the MESA_XSYNC env var
first will force Xlib to operate synchronously and should make it easier
to locate the problem.
-Brian
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
