|
From: Jeremy F. <je...@go...> - 2004-02-29 21:51:17
|
On Sat, 2004-02-28 at 10:13, Tom Hughes wrote: > *************** > *** 2 **** > --- 3,7 ---- > + valgrind's libpthread.so: init_libc_tsd_keys: lock > + Please report this bug at: valgrind.kde.org > > Which is a bit odd, because from looking at the code it means that > the attempt to lock the mutex in init_libc_tsd_keys is failing for > some reason. Yes, this is the result of some unwanted recursion. Um. What was it. Ah yes: my_malloc ends up calling real malloc(), which on some libc's ends up calling init_libc_tsd_keys recursively. The mutex is already held, so it fails the second time through. my_malloc could use the MALLOC client request, but that causes other problems, which I don't remember completely. Some dependency on whether the tool you have is overriding malloc or not. J |