check the mem_log level to be less than debug value, in order to get the
mem logs printed.
In the mean while I will try to take a look at the issue you mentioned.
Thanks and regards,
bogdan
Vadim Berezniker wrote:
No, I don't believe I got any such message (but I can double check a bit
later).
However, all strings returned from unixodbc with memory debugging
enabled are not valid.
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 4:55 AM
To: Vadim Berezniker
Cc: devel@openser.org
Subject: Re: [Devel] unixodbc memory problem
Hi Vadim,
do you get any logs with "BUG" from the mem. debugger?
regards,
bogdan
Vadim Berezniker wrote:
If I enable memory debugging, the unixodbc module stops working
properly.
There seems to be a problem with the way result sets are converted
internally (convert_rows):
A list is allocated with a copy of the columns in the result set
str2val stores a pointer to data in the list for DB_STRING, DB_STR and
DB_BLOB values
the list is destroyed and the data is unallocated. the string pointers
in the result set are no longer valid
------------------------------------------------------------------------
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
