Re: Memory leak in ld.so-2.4

2007-04-19 Thread Seweryn Habdank-Wojewódzki
Dears > > A piece of valgrind log file is: > > > > ==9293==    at 0x402073E: calloc (in > > /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) > > ==9293==    by 0x40105C8: allocate_dtv (in /lib/ld-2.4.so) > > ==9293==    by 0x401068B: _dl_allocate_tls (in /lib/ld-2.4.so) > > ==9293==    by 0x405

Re: Memory leak in ld.so-2.4

2007-04-19 Thread Ian Lance Taylor
Seweryn Habdank-Wojewódzki <[EMAIL PROTECTED]> writes: > There is a memory leak in ld.so. > > A piece of valgrind log file is: > > ==9293==    at 0x402073E: calloc (in > /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) > ==9293==    by 0x40105C8: allocate_dtv (in /lib/ld-2.4.so) > ==9293==    

Memory leak in ld.so-2.4

2007-04-19 Thread Seweryn Habdank-Wojewódzki
Dears There is a memory leak in ld.so. A piece of valgrind log file is: ==9293==    at 0x402073E: calloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==9293==    by 0x40105C8: allocate_dtv (in /lib/ld-2.4.so) ==9293==    by 0x401068B: _dl_allocate_tls (in /lib/ld-2.4.so) ==9293==    by