[Xcb] valgrind reports an error

[Jamey Sharp]

On Wed, Dec 14, 2005 at 11:48:46PM +0100, Vincent Torri wrote:
> Hey,

Hi Vincent!

> with this program:
> http://www.iecn.u-nancy.fr/~torri/files/xcb/xcb_request_test.c
> 
> valgrind reports me an error :
> 
> ==8289== 1 errors in context 1 of 1:
> ==8289== Syscall param write(buf) points to uninitialised byte(s)
> ==8289==    at 0x1B9F2923: write (in /lib/tls/libc-2.3.3.so)
> ==8289==    by 0x1B914DEB: _xcb_write (xcb_util.c:249)
> ==8289==    by 0x1B912D52: _xcb_out_write (xcb_out.c:194)
> ==8289==    by 0x1B912677: _xcb_conn_wait (xcb_conn.c:227)
> ==8289==    by 0x1B9131C8: _xcb_out_flush (xcb_out.c:267)
> ==8289==    by 0x1B913376: XCBWaitForReply (xcb_in.c:80)
> ==8289==    by 0x1B916DC9: XCBGetInputFocusReply (xproto.c:1430)
> ==8289==    by 0x1B914BAC: XCBSync (xcb_util.c:196)
> ==8289==  Address 0x1BA69719 is 4297 bytes inside a block of size 8472
> alloc'd
> ==8289==    at 0x1B8FEEDE: calloc (vg_replace_malloc.c:279)
> ==8289==    by 0x1B9122B2: XCBConnectToFD (xcb_conn.c:137)
> ==8289==    by 0x1B914A5C: XCBConnect (xcb_util.c:163)
> ==8289==    by 0x8048764: main (xcb_request_test.c:19)
> 
> I have updated xcb from cvs.
> 
> Have I forgotten something in my code ?

Probably not. XCB doesn't yet zero padding bytes, so this kind of
valgrind complaint in xcb_out.c is expected. Jim Gettys and Carl Worth
have both argued that this should be fixed, and I've been meaning to get
around to it, but it's been low priority.

--Jamey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/xcb/attachments/20051224/3beea9f3/attachment.pgp