FreeTDS Development Group

["Frediano Ziglio" <freddy77 AT gmail.com>]

2008/11/26  <mtbrown88 AT comcast.net>:
>
>
> Hi all,
>
>
>
> Is there a known memory leak or memory accumulation issue with ct_cmd_alloc 
> / ct_cmd_drop?
>
>
>
> I'm writing a program to poll a database as regular intervals and it 
> gradually accumulates memory (seen via top).
>
>
>
> Below is source code to attempt and isolate the problem, compiled with the 
> following command:
>
>    cc -o ctlib_leak ctlib_leak.c /usr/local/lib/libct.a /usr/lib/librt.a
>
>
>
> I am linking with the archive libraries to run against Purify if necessary.
>
>
> Quickest way to see memory eaten up (via top) is to direct stdout and 
> stderr to /dev/null (so output doesn't slow down processing).
>
>
>
> Thanks in advance for any input or suggestions.  I can dig deeper, but 
> wanted to know if this is a known issue.
>
>
>
> Regards, Michael
>
>
>
>
>
> Here is the source code for ctlib_leak.c:
>

... code stripped down ...

Hi,
  I ran the program (it compile fine without problems, I just changed
server, port and account) with Valgrind under Linux using all protocol
(4.2, 5.0, 7.0 and 8.0) with different server but I got no leaks.
Which platform are you using? Which configurations?

freddy77