|
From: Nicholas N. <nj...@ca...> - 2003-12-01 16:23:05
|
On Mon, 1 Dec 2003, Simon Josefsson wrote: > Yes, I read FAQ #1, but I'm using the latest glibc (which glibc > versions are considered too old/buggy in FAQ #1, btw?). But why > doesn't the problem occur when I link with other libraries? The glibc > is the same. I have been using valgrind extensively on other projects > on this machine, so it must be some interaction between this > particular library, valgrind and possibly the system. All libraries > are built on the same machine, with the same compiler etc. I guess that libshishi allocates some memory upon startup (in its .init section, even if it's not used at all), and then something goes wrong later when it tries to deallocate it... which seems to be triggered by __libc_freeres. I don't know anything beyond that. N |