Re: [Mesa3d-dev] GLX leakage

2006-07-15 Thread Tilman Sauerbeck
Ian Romanick [2006-07-13 14:30]: > Tilman Sauerbeck wrote: > > Dave Airlie [2006-07-13 20:12]: > > > >>>http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2&r2=1.3 > >>> > >>>The commit comment just says: > >>>"3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to > >>

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tilman Sauerbeck wrote: > Dave Airlie [2006-07-13 20:12]: > >>>http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2&r2=1.3 >>> >>>The commit comment just says: >>>"3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to >>>

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Tilman Sauerbeck
Dave Airlie [2006-07-13 20:12]: > > > > http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2&r2=1.3 > > > > The commit comment just says: > > "3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to > > version 3.2, adds full support and fifo code for 3dfx hardware,

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Dave Airlie
> > http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2&r2=1.3 > > The commit comment just says: > "3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to > version 3.2, adds full support and fifo code for 3dfx hardware, > and updates the device driver to work

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Tilman Sauerbeck
Ian Romanick [2006-07-13 07:46]: > Tilman Sauerbeck wrote: > > I've been valgrinding around a bit lately, and noticed this: > > > > ==9215== 20 (16 direct, 4 indirect) bytes in 1 blocks are definitely lost > > in loss record 8 of 22 > > ==9215==at 0x401B4D1: malloc (in > > /usr/lib/valgrind/

Re: [Mesa3d-dev] GLX leakage

2006-07-13 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tilman Sauerbeck wrote: > Hi, > I've been valgrinding around a bit lately, and noticed this: > > ==9215== 20 (16 direct, 4 indirect) bytes in 1 blocks are definitely lost in > loss record 8 of 22 > ==9215==at 0x401B4D1: malloc (in > /usr/lib/val

[Mesa3d-dev] GLX leakage

2006-07-12 Thread Tilman Sauerbeck
Hi, I've been valgrinding around a bit lately, and noticed this: ==9215== 20 (16 direct, 4 indirect) bytes in 1 blocks are definitely lost in loss record 8 of 22 ==9215==at 0x401B4D1: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==9215==by 0x412ADE6: driCreateDisplay (dr