[gtkmm] Memoryleaks

[Pierre Lor <pierre lor pandora be>]

Hi,

I have tried Valgrind 1.9.3 on the base.cc program explained in the docs of 
gktmm 2.2.

valgrind --leak-check=yes base

I have following result:

==4782== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
==4782== Copyright (C) 2002, and GNU GPL'd, by Julian Seward.
==4782== Using valgrind-1.9.3, a program instrumentation system for x86-linux.
==4782== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==4782== Estimated CPU clock rate is 734 MHz
==4782== For more details, rerun with: -v
==4782==
==4782==
==4782== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 2)
==4782== malloc/free: in use at exit: 227254 bytes in 3872 blocks.
==4782== malloc/free: 6104 allocs, 2233 frees, 484286 bytes allocated.
==4782== For counts of detected errors, rerun with: -v
==4782== searching for pointers to 3872 not-freed blocks.
==4782== checked 12402600 bytes.
==4782==
==4782== 16 bytes in 1 blocks are definitely lost in loss record 15 of 77
==4782==    at 0x4015D50F: malloc (vg_clientfuncs.c:100)
==4782==    by 0x4015DA26: realloc (vg_clientfuncs.c:265)
==4782==    by 0x409FE14A: __argz_append (in /lib/libc.so.6)
==4782==    by 0x409AB5F8: __newlocale (in /lib/libc.so.6)
==4782==
==4782== 39 bytes in 2 blocks are definitely lost in loss record 26 of 77
==4782==    at 0x4015D50F: malloc (vg_clientfuncs.c:100)
==4782==    by 0x40B2A5B7: resolve_name (in /usr/X11R6/lib/libX11.so.6.2)
==4782==    by 0x40B2ACE6: _XlcLocaleDirName (in /usr/X11R6/lib/libX11.so.6.2)
==4782==    by 0x40B249E2: _XlcDynamicLoad (in /usr/X11R6/lib/libX11.so.6.2)
==4782==
==4782== 800 bytes in 20 blocks are possibly lost in loss record 60 of 77
==4782==    at 0x4015D999: calloc (vg_clientfuncs.c:242)
==4782==    by 0x4086839B: g_malloc0 (gmem.c:153)
==4782==    by 0x4082495D: type_node_any_new_W (gtype.c:290)
==4782==    by 0x40824C74: type_node_fundamental_new_W (gtype.c:367)
==4782==
==4782== LEAK SUMMARY:
==4782==    definitely lost: 55 bytes in 3 blocks.
==4782==    possibly lost:   800 bytes in 20 blocks.
==4782==    still reachable: 226399 bytes in 3849 blocks.
==4782==         suppressed: 0 bytes in 0 blocks.
==4782== Reachable blocks (those to which a pointer was found) are not shown.
==4782== To see them, rerun with: --show-reachable=yes
==4782==

Is there a problem with Valgrind or does Gtkmm leak memory ?

Pierre Lor