|
From: David E. <tw...@us...> - 2003-08-06 07:15:24
|
On Wed, 2003-08-06 at 06:15, Rob Kramer wrote:
> Hi,
>
> When valgrinding my program, I get the following 2 loss records (sorry for
> lousy wrapping):
>
> ==3356== 22248 bytes in 9 blocks are possibly lost in loss record 5 of 6
> ==3356== at 0x40013A09: __builtin_new (vg_replace_malloc.c:172)
> ==3356== by 0x40013A60: operator new(unsigned) (vg_replace_malloc.c:185)
> ==3356== by 0x402F253F: std::__default_alloc_template<true,
> 0>::_S_chunk_alloc(unsigned, int&)
> (/home/rob/gcc/build/i486-suse-linux/libstdc++-v3/include/bits/stl_alloc.h:109)
> ==3356== by 0x402F2448: std::__default_alloc_template<true,
> 0>::_S_refill(unsigned)
> (/home/rob/gcc/build/i486-suse-linux/libstdc++-v3/include/bits/stl_alloc.h:561)
> ==3356==
> ==3356==
> ==3356== 79218 bytes in 350 blocks are still reachable in loss record 6 of 6
> ==3356== at 0x40013A09: __builtin_new (vg_replace_malloc.c:172)
> ==3356== by 0x40013A60: operator new(unsigned) (vg_replace_malloc.c:185)
> ==3356== by 0x402F253F: std::__default_alloc_template<true,
> 0>::_S_chunk_alloc(unsigned, int&)
> (/home/rob/gcc/build/i486-suse-linux/libstdc++-v3/include/bits/stl_alloc.h:109)
> ==3356== by 0x402F2448: std::__default_alloc_template<true,
> 0>::_S_refill(unsigned)
> (/home/rob/gcc/build/i486-suse-linux/libstdc++-v3/include/bits/stl_alloc.h:561)
>
> I can't see where they originate.. Should I worry about this, or is this just
> an internal libstdc++ cleanup issue?
>
> Command line:
>
> valgrind -v --leak-check=yes --show-reachable=yes
> --suppressions=/usr/il/ismncc/rob.supp /usr/il/ismncc/ismncc
Add --num-callers=30 and run again. Increase number if needed.
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
CalcEm - http://calcem.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
SetiWrapper - http://setiwrapper.sourceforge.net
|