On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
> However, I think you may be tickling a latent bug in the DRI. It's
> possible that all the other drives have just avoided this bug so far.
>
> I looked at DRICloseScreen and I don't see that the DRIClipNotify
> wrapper is being removed. There are other unwraps missing as well.
>
> Can you send me a back trace from a static debuggable server? Let me
> know if you need help building this.
Could you tell me how to build a static server or point me to a HOWTO?
Meanwhile, here's a backtrace from the X server built from the branch. It
looks like the ClipNotify wrapper is being called when pDRIPriv is null,
though I'm not sure why I wouldn't have run into this before...
Program received signal SIGSEGV, Segmentation fault.
DRIClipNotify (pWin=0x85d3a60, dx=0, dy=0) at dri.c:1732
1732 if(pDRIPriv->wrap.ClipNotify) {
(gdb) bt
#0 DRIClipNotify (pWin=0x85d3a60, dx=0, dy=0) at dri.c:1732
#1 0x080c9009 in MapWindow (pWin=0x85d3a60, client=0x81d56a8) at window.c:2864
#2 0x080c5ee8 in InitRootWindow (pWin=0x85d3a60) at window.c:522
#3 0x080bf39c in main (argc=4, argv=0xbffff9d4, envp=0xbffff9e8) at main.c:439
#4 0x40072647 in __libc_start_main (main=0x80bee9c <main>, argc=4,
ubp_av=0xbffff9d4, init=0x806cc08 <_init>, fini=0x8174c80 <_fini>,
rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffff9cc)
at ../sysdeps/generic/libc-start.c:129
(gdb) info locals
pWin = 0x85d3a60
pScreen = 0x85d3748
pDRIPriv = 0x0
pDRIDrawablePriv = 0x0
--
Leif Delgass
http://www.retinalburn.net
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Bringing you mounds of caffeinated joy.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
