Re: [Valgrind-users] newbie question for a change ;)

[Nicholas N. <nj...@ca...>]

On Fri, 11 Apr 2003, Mathieu Malaterre wrote:

> 1. What does : "valgrind's libpthread.so: KLUDGED call to:
> pthread_cond_destroy" means ?
>
> I wasn't able to translate KLUDGED ...

'kludged' means something like 'faked' or 'handled semi-bogusly'.  I'm not
sure exactly what it means in this context, but some parts of V's
libpthread.so aren't really complete.  It may not matter for your program,
I think.

> 2. And what does
>
> " Syscall param writev(vector[...]) contains uninitialised or
> unaddressable byte(s)
> at 0x40237951: my_do_syscall3 (vg_libpthread.c:2389)
> by 0x40236BA8: vgIntercept_writev (vg_libpthread.c:2055)
> by 0x4017BF68: __writev (vg_intercept.c:287)
> by 0x43246B45: (within /usr/X11R6/lib/libX11.so.6.2)
> Address 0x413C7FD8 is 124 bytes inside a block of size 2048 alloc'd
> at 0x40165F4D: calloc (vg_clientfuncs.c:242)
> by 0x4321D6FE: XOpenDisplay (in /usr/X11R6/lib/libX11.so.6.2)
> by 0x430BEB12: gdk_init_check (in /usr/lib/libgdk-1.2.so.0.9.1)
> by 0x42EC3CA1: gtk_init_check (in /usr/lib/libgtk-1.2.so.0.9.1)"
>
> means ?

Some code within libX11.so.2 is calling the sys call writev() with some
bogus memory -- in this case, it looks like some of the memory block
passed to writev() (via a pointer) is uninitialised.  The 2nd half of the
error tells you where the block in question was allocated.

If it's in libX11.so, that might be out of your control? in which case you
could suppress it if it does not affect your program, but it sounds like
it unfortunately does in this case.

N