Menu
▾
▴
Re: [Valgrind-users] gtk "hello world" memory leak
|
From: Dan K. <da...@ke...> - 2009-08-13 14:02:03
|
On Thu, Aug 13, 2009 at 4:37 AM, Lukasz Gromotowicz<gr...@gm...> wrote: >> ==5425== Syscall param writev(vector[...]) points to uninitialised byte(s) >> ==5425== at 0x691FE8: writev (in /lib/libc-2.6.so) >> ==5425== by 0x85BA3D: (within /usr/lib/libX11.so.6.2.0) >> ==5425== by 0x85B82E: _X11TransWritev (in /usr/lib/libX11.so.6.2.0) >> ==5425== by 0x861558: _XSend (in /usr/lib/libX11.so.6.2.0) >> ==5425== by 0x85244A: XQueryExtension (in /usr/lib/libX11.so.6.2.0) >>... >>==5425== by 0xAF46B4: gdk_display_open (in /usr/lib/libgdk-x11-2.0.so.0.1000.14) Offhand, that looks like an issue in the system X or gtk libraries. You can probably safely suppress it. We suppress four or so gtk warnings here. See the top part of http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/memcheck/suppressions.txt?revision=23220 for our list. http://www.gnome.org/~johan/gtk.suppression is another list I've seen. - Dan |
