From: Mathieu M. <Mat...@cr...> - 2003-04-11 17:31:42
|
Hi all, Once again I'll start by saying that I am a newbie and please bear with me...blabla Ok now I introduced myself ;) I have two questions: 1. What does : "valgrind's libpthread.so: KLUDGED call to: pthread_cond_destroy" means ? I wasn't able to translate KLUDGED ... 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 ? Please note that this message isn't shown if I start my app with option '--sync', which mean that X whill be started in synchronize mode : XSynchronize(display,True). If this sole message doesn't give any clue on what the problem is, could someone told me what to do then (use gtk debug lib, X debug lib -if such beast exists-, ...) I was running valgrind on my linux box with lastest nvidia driver with the following command line: __GL_FORCE_GENERIC_CPU=1 valgrind -v --leak-check=yes python2.2 wxMyApp.py thanks, mathieu Ps: I am trying to debug an app that works perfectly if using '--sync' option but freeze my X session if started without '--sync' option. -- Mathieu Malaterre CREATIS 28 Avenue du Doyen LEPINE B.P. Lyon-Montchat 69394 Lyon Cedex 03 http://www.creatis.insa-lyon.fr/~malaterre/ |