On Mar 28, 2009, at 9:45 PM, Peter Stuge <pe...@stuge.se> wrote:
> Daniel Johnson wrote: >>>> ** MEMORY FAILURE >>>> Leak detected: memory still allocated: 188 bytes >>>> At 30c264, there's 188 bytes. >>>> allocated by ../../curl/lib/ssh.c:281 >>>> >>>> which is in libcurl's LIBSSH2_ALLOC_FUNC. > > .. >> Too bad there's no OS X port of valgrind yet. > > You can find out more information with a ghetto hack: > > Add two parameterr to LIBSSH2_ALLOC_FUNC, rename it, and add a macro > which passes __FILE__ or __func__ and __LINE__ as those parameters, > and print them out along with the allocated address in the renamed > LIBSSH2_ALLOC_FUNC. Poor man's dylib preload. > > Then simply match the return address with the Leak detected message > to find out which alloc is unmatched. Maybe it is the same leak > Jean-Louis found? > > > //Peter > > --- > --- > --- > --------------------------------------------------------------------- > _______________________________________________ > libssh2-devel mailing list > libssh2-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libssh2-devel Thanks, I'll look into this once I have a computer again. It picked a most inconvienent time to die. Typical. Daniel ------------------------------------------------------------------------------ _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
