Re: Memory leak or memory accumulation with freetds-0.82 ctlib's ct_cmd_alloc / ct_cmd_drop?

Hi freddy77, 



Ran valgrind and purify against ctlib_leak...no memory leaks found.  After further investigation, the allocated memory (via ctlib_leak) is going into the cache pool, so my memory leak must be elsewhere (not in the ctlib_leak source code).  I'll expand my search to the rest of my source code again. 



Thanks for the assistance and for pointing me to valgrind.  I've used purify, but hadn't used valgrind before. 



Cheers, 

mtbrown88 




----- Original Message ----- 
From: "Frediano Ziglio" <[email protected]> 
To: "FreeTDS Development Group" <[email protected]> 
Sent: Saturday, November 29, 2008 3:49:27 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [freetds] Memory leak or memory accumulation with freetds-0.82 ctlib's ct_cmd_alloc / ct_cmd_drop? 

Il giorno gio, 27/11/2008 alle 17.01 +0000, [email protected] ha 
scritto: 
> 
> Hi freddy77, 
> 
> 
> 
> Thanks for testing it.  I am running Red Hat Enterprise Linux 4 Update 7 -- uname -a output: 
> 
>    Linux devbox.localdomain 2.6.9-78 EL #1 Wed Jul 9 15:27:01 EDT 2008 i686 athlon i386 GNU/Linux 
> 
> and top shows all of the memory slowly being used up. 
> 
> 
> 
> Thanks, 
> 
> mtbrown88 
> 

Could you try to install valgring and execute a 

valgrind --tool=memcheck --leak-check=yes --show-reachable=yes 
--num-callers=20 ./ctlib_leak 

it should report leaks and where they happen. Is better to compile 
FreeTDS (at least) with debugging informations. 

freddy77 


_______________________________________________ 
FreeTDS mailing list 
[email protected] 
http://lists.ibiblio.org/mailman/listinfo/freetds 
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds