http://bugs.freedesktop.org/show_bug.cgi?id=7205





------- Comment #27 from [EMAIL PROTECTED]  2007-03-02 06:02 PST -------
(In reply to comment #26)
> > OK, If we're deleting a framebuffer object while someone is still pointing 
> > to
> > it, this assertion might help catch it:

So far it wasn't hit for me.

(In reply to comment #24)
> The attached test case never crashed for me (only for the contributor), but
> exhibits the same stray pointers when I use my patch from attachment #8501.

Tested with current git, both Mesa and complete X environment.

Valgrind shows few warnings when running the test case, and seems to freeze
(100% CPU). It probably has to emulate and verify a lot of memory accesses, or
I hit a bug in valgrind:

==15227== 
==15227== Syscall param writev(vector[...]) points to uninitialised byte(s)
==15227==    at 0x4260492: do_writev (in /lib/libc-2.5.so)
==15227==    by 0x81B5A7D: _XSERVTransSocketWritev (Xtranssock.c:2192)
==15227==    by 0x81B477E: _XSERVTransWritev (Xtrans.c:914)
==15227==    by 0x81AF969: FlushClient (io.c:1057)
==15227==    by 0x81B00F3: FlushAllOutput (io.c:809)
==15227==    by 0x808901E: Dispatch (dispatch.c:525)
==15227==    by 0x80707A4: main (main.c:469)
==15227==  Address 0x63FAB3C is 36 bytes inside a block of size 4,096 alloc'd
==15227==    at 0x40233F0: malloc (in
/usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==15227==    by 0x81B1C96: Xalloc (utils.c:1351)
==15227==    by 0x81AF596: AllocateOutputBuffer (io.c:1197)
==15227==    by 0x81AFE3F: WriteToClient (io.c:916)
==15227==    by 0x8082626: SendConnSetup (dispatch.c:3940)
==15227==    by 0x808273F: ProcEstablishConnection (dispatch.c:3988)
==15227==    by 0x8088FBE: Dispatch (dispatch.c:503)
==15227==    by 0x80707A4: main (main.c:469)
Cleaning up stray priv pointers to 0x661ef28 in context 0x63fcac0
Cleaning up stray xmesa pointers to buffer 0x6a4e5c8 in context 0x63fcac0
==15227== Warning: set address range perms: large range 134217728 (undefined)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to