FreeTDS Development Group

[<Mitchell_Freed AT McAfee.com>]

I found the issue, it was on my end. Sorry for the confusion.

- Mitch

On 03/01/2012 02:31 PM, Frediano Ziglio wrote:

Tried to reproduce without success. Valgrind is always happy too :(
Can you try to enable logging?

Frediano


2012/3/1  <Mitchell_Freed AT mcafee.com><mailto:Mitchell_Freed AT mcafee.com>:
> I'll see if I can track down exactly where it's getting confused.
>
> - Mitch
>
> On 02/29/2012 06:44 PM, James K. Lowden wrote:
>
> On Wed, 29 Feb 2012 08:58:39 -0800
> <Mitchell_Freed AT McAfee.com><mailto:Mitchell_Freed AT McAfee.com><mailto:Mitchell_Freed AT McAfee.com>
>  wrote:
>
>> The error occurs in mem.c when trying to free the TDSLOGIN*. I
>> noticed that the TDSLOGIN* allocated in tds_alloc_login is a
>> different pointer than the one being passed to tds_free_login.
>> Looking into it a bit closer the tds_free_login is failing on the
>> TDSLOGIN* allocated from tds_alloc_connection -- if that helps.
>
> On the error path from a connection failure, ct_connect() calls a host
> of free_* routines, some of which call other freers, some through
> pointers.  It's possible something goes wrong.  Not obvious, but
> possible.
>
> You could attack it through your malloc(3).  Most C standard libraries
> have ways to make invalid frees fail in a noisy way.
>
> Thanks for reporting the problem...
>
> --jkl
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org<mailto:FreeTDS AT lists.ibiblio.org><mailto:FreeTDS AT lists.ibiblio.org>
> http://lists.ibiblio.org/mailman/listinfo/freetds
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org<mailto:FreeTDS AT lists.ibiblio.org>
> http://lists.ibiblio.org/mailman/listinfo/freetds
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org<mailto:FreeTDS AT lists.ibiblio.org>
http://lists.ibiblio.org/mailman/listinfo/freetds