Hello,


I am running a memory leak reporting program (written in C) that essentially does malloc() replacement to detect/report boundary overflow conditions. The tool should work against C and C++ programs. This has worked fine on older versions of SuSe. Starting with SLES8, a simple hello world program, written in C++, run with the memory debugger program is reporting (false??) memory leaks. This is reported as the following sample at the end of this note. Is this something to do with libstd++ is allocating buffers in the new v3.2? I have read some of the GNU libstdc++ pages, that other memory debugging tools have reported false memory leaks, but it seems more geared for new/delete and C++ rather than issue(s) with C libraries (malloc). If anyone has any information on, this would be most appreciated.
Thanks,

WARNING: Memory leak
Address 0x1000012ef80, size 128
Allocated by malloc at
??:0(??)/lib64/libc.so.6(malloc+0x38)[0x1000023bd14]
??:0(??)/lib64/libc.so.6(__newlocale+0x336)[0x100001eb116]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt6locale5facet18_S_create_c_localeERP15__locale_structPKcS2_+0x20)[0x100000d7da0]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt6locale5_ImplC1EPPNS_5facetEmb+0x56)[0x100000b38a2]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt6locale7classicEv+0xc2)[0x100000929ee]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt6localeC1Ev+0x70)[0x10000090eac]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt13basic_filebufIcSt11char_traitsIcEEC2Ev+0x90)[0x1000007def8]
??:0(??)/usr/lib64/libstdc++.so[0x1000007c734]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt8ios_base4Init13_S_ios_createEb+0x542)[0x1000008867a]
??:0(??)/usr/lib64/libstdc++.so(_ZNSt8ios_base4InitC1Ev+0x56)[0x10000088872]
??:0(??)/usr/lib64/libstdc++.so[0x10000087ef4]
??:0(??)/usr/lib64/libstdc++.so[0x10000087f60]
??:0(??)/usr/lib64/libstdc++.so[0x100000e0e70]
??:0(??)/usr/lib64/libstdc++.so[0x100000733ba]
??:0(??)[0x1000000d2e0]
??:0(??)[0x1000000d3da]
??:0(??)[0x10000001daa]