Hi Jeff, > -----Original Message----- > From: J. Jeff Roberts [mailto:[EMAIL PROTECTED] > Sent: Freitag, 25. Juli 2003 19:31 > To: [EMAIL PROTECTED] > Subject: BoundsChecker and SAP ODBC Driver > > > While tracking down our own leaks, I found that BoundsChecker believes > that we're leaking memory, handles and semaphores from the SAP ODBC > driver (sqluser74.dll, sqlod32.dll). > > If I run the small program below to simply connect to a database and > disconnect, BoundsChecker reports two regular memory leaks, one for > something allocated by MapViewOfFile(), and 116 "nested leaks".
At our site we use Purify under Windows for such tasks. Actually Purify reports similar things as mentioned in your mail, but I don't believe, that these are leaks, because - our OS/machine independent runtime environment (that is of course used by the ODBC driver) has some initialize functions but no finalize functions. I.e. some resources (e.g. some thread local storage or semaphores etc.) is freed implicitely by ending a program. - other resources like the driver trace file cannot be closed since there is no "stop ODBC processing"-function (and therefore even if our runtime would have a finalize function we couldn't call it). > Finally, it always claims that I've leaked the SQLHENV and > the SQLHDBC. This Purify does not report. I used the driver manager 3.520.9030.0 which should be part of the current MDAC 2.7. Do you have the same? Of course there still might be (or shall I say: are) bugs and maybe resource leaks in the ODBC driver. If you think that you have found one, please try to exhibit the leak by a small program for bug fixing. Regards Thomas PS: An excellent tool for Linux is valgrind! ---------------------------------------------- Dr. Thomas K�tter SAP DB, SAP Labs Berlin Hurry up, SAP DB is open source www.sapdb.org _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
