|
From: Mathieu M. <mat...@ki...> - 2004-08-16 19:46:28
|
Hello,
Could someone confirm that this mem leak is in X11:
Using:
#include <X11/Xlib.h>
#include <X11/Xutil.h>
int main()
{
Display *display = XOpenDisplay( NULL );
XCloseDisplay(display);
}
valgrind is reporting:
==20041== 200 bytes in 1 blocks are definitely lost in loss record 2 of 2
==20041== at 0x3C01E274: malloc (vg_replace_malloc.c:105)
==20041== by 0x3CCCCE06: my_malloc (vg_libpthread.c:334)
==20041== by 0x3CCCFAB3: get_or_allocate_specifics_ptr
(vg_libpthread.c:1591)
==20041== by 0x3CCCFC3C: pthread_key_create (vg_libpthread.c:1628)
==20041== by 0x8BB547: init (in /lib/libdl-2.3.2.so)
==20041== by 0x3CCD028F: pthread_once (vg_libpthread.c:1730)
==20041== by 0x8BB4FC: _dlerror_run (in /lib/libdl-2.3.2.so)
==20041== by 0x8BB0A3: dlsym (in /lib/libdl-2.3.2.so)
==20041== by 0x3CCD0ACE: __errno_location (vg_libpthread.c:1948)
==20041== by 0x8F29D6: _XRead (in /usr/X11R6/lib/libX11.so.6.2)
==20041== by 0x8E4924: XOpenDisplay (in /usr/X11R6/lib/libX11.so.6.2)
==20041== by 0x80488B9: main (foo.cxx:6)
Is this correct, can I safely ignore this leak ?
Thanks
Mathieu
|
|
From: Tom H. <th...@cy...> - 2004-08-16 19:58:53
|
In message <412...@ki...>
Mathieu Malaterre <mat...@ki...> wrote:
> Could someone confirm that this mem leak is in X11:
I can confirm that it isn't - it's actually in valgrind. It is
supposed to be suppressed by the default suppressions. Some older
versions may not manage to supress it on some systems however.
It doesn't really matter because the memory in question could only
ever be freed at exit anyway.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|