I've downloaded the latest MyODBC driver and iODBC manager and
tested them for memory leakage. Unfortunately, the leakage
I reported months ago is still there. Even worse, it seems to
The strange thing is that the leakage only occurs on Linux,
not with the latest driver for Win95, yet both platforms run the
same test code.
I also checked the test code with other drivers directly and
through the iODBC manager: neither the drivers, nor the iODBC
manager leak memory and this makes me pretty convinced that the
leakage must be located somewhere in the Unix part of the
I looked around the code a bit, but all I found was that
a malloc in prepare.c is done via my_malloc(), but freed via free(),
instead of my_free(). Changing it didn't result in any improvement
Can anybody comment on this ?
Y2000: 211 days left
Python Pages: http://www.lemburg.com/python/