Does anyone care about uninitialized bytes?
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
Hi,
On Wed, Feb 23, 2011 at 07:01:04PM +0200, Pauli wrote:
diff --git a/hw/xfree86/dri2/dri2ext.c b/hw/xfree86/dri2/dri2ext.c
index 4e48e65..725823e 100644
--- a/hw/xfree86/dri2/dri2ext.c
+++ b/hw/xfree86/dri2/dri2ext.c
@@ -227,11 +227,15 @@ send_buffers_reply(ClientPtr client, DrawablePtr
On 02/03/11 11:37 +, ext Daniel Stone wrote:
Hi,
On Wed, Feb 23, 2011 at 07:01:04PM +0200, Pauli wrote:
diff --git a/hw/xfree86/dri2/dri2ext.c b/hw/xfree86/dri2/dri2ext.c
index 4e48e65..725823e 100644
--- a/hw/xfree86/dri2/dri2ext.c
+++ b/hw/xfree86/dri2/dri2ext.c
@@ -227,11
On Wed, Mar 02, 2011 at 01:41:25PM +0200, Pauli Nieminen wrote:
On 02/03/11 11:37 +, ext Daniel Stone wrote:
On Wed, Feb 23, 2011 at 07:01:04PM +0200, Pauli wrote:
diff --git a/hw/xfree86/dri2/dri2ext.c b/hw/xfree86/dri2/dri2ext.c
index 4e48e65..725823e 100644
---
From: Pauli Nieminen ext-pauli.niemi...@nokia.com
This fixes following valgrind reported error about padding being uninitialised.
==== Syscall param writev(vector[...]) points to uninitialised byte(s)
====at 0x4AB7054: writev (writev.c:51)
====by 0x5E237: _XSERVTransWritev
