Shibboleth Developers

[André Cruz <>]

On 2008/01/03, at 18:42, Scott Cantor wrote:

> Does valgrind actually say what the leak is? I've never noticed it  
> report
> anything significant I could trace, not since I used it a long time  
> ago to
> fix a few leaks.

The closest I get is:

==9218== 8,468,928 bytes in 1,044 blocks are definitely lost in loss  
record 33 of 33
==9218==    at 0x4A1BDEB: malloc (vg_replace_malloc.c:207)
==9218==    by 0x62A9DD1: xprt_register (in /lib/libc-2.3.6.so)
==9218==    by 0x62AAD51: makefd_xprt (in /lib/libc-2.3.6.so)
==9218==    by 0x4058C5: SharChild::svc_create() (shar-utils.cpp:164)
==9218==    by 0x405B4A: SharChild::run() (shar-utils.cpp:130)
==9218==    by 0x405F90: shar_client_thread(void*) (shar-utils.cpp:89)
==9218==    by 0x60ACF19: start_thread (in /lib/libpthread-2.3.6.so)
==9218==    by 0x62855D1: clone (in /lib/libc-2.3.6.so)

1044 is the number of times I ran the client.

André