I'm in the process of moving DRM CVS to git, can people avoid using CVS from
now on...
When I get the last admin help the repo will be (in a few hours):
git://anongit.freedesktop.org/git/mesa/drm
I've decided to put the drm under the mesa project on fd.o as the dri project
is pretty much
-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
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7353
[EMAIL PROTECTED] changed:
What|Removed |Added
Hanno Böck wrote:
In various dri-drivers, DO_DEBUG is defined to 1.
Shouldn't this be defaulted off and only enabled via -DDO_DEBUG on CFLAGS?
(suggested Patch attached)
diff -Naur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Böck wrote:
In various dri-drivers, DO_DEBUG is defined to 1.
Shouldn't this be defaulted off and only enabled via -DDO_DEBUG on CFLAGS?
(suggested Patch attached)
It defaults to 1 because it doesn't actually enable debugging. It
enables
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
http://cvsweb.xfree86.org/cvsweb/xc/lib/GL/glx/glxext.c.diff?r1=1.2r2=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 with
-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.2r2=1.3
The commit comment just says:
3377. DRI megapatch. This moves mesa to xc/extras, updates Mesa to
version 3.2,
Am Donnerstag, 13. Juli 2006 17:46 schrieb Ian Romanick:
It defaults to 1 because it doesn't actually enable debugging. It
enables a variable that allows the user to enable debugging at run-time.
By default the driver_DEBUG variables are set to zero, but
environment variables (or GDB!) can
