RE: Memory leak in client-library's mysql_init() and mysql_real_connect() - Sinisa Milivojevic - com.mysql.lists.bugs

11 messages in com.mysql.lists.bugsRE: Memory leak in client-library's m...

From	Sent On	Attachments
Mikko Noromaa	09 May 2002 10:54
Sinisa Milivojevic	10 May 2002 05:16
Mikko Noromaa	10 May 2002 07:22
Sinisa Milivojevic	10 May 2002 09:08
Mikko Noromaa	10 May 2002 09:51
Sinisa Milivojevic	10 May 2002 09:57
Sinisa Milivojevic	10 May 2002 10:08
Venu	10 May 2002 15:11
Mikko Noromaa	11 May 2002 08:06
Michael Widenius	15 May 2002 01:11
Michael Widenius	15 May 2002 01:45

Subject:	RE: Memory leak in client-library's mysql_init() and mysql_real_connect()
From:	Sinisa Milivojevic (sin...@mysql.com)
Date:	05/10/2002 10:08:29 AM
List:	com.mysql.lists.bugs

Mikko Noromaa writes:

Hi,

In my debug build, I use the mysqlclient.lib library from \mysql\lib\debug. I assume it has been built with maximum debug code. In my release build, however, I use mysqlclient.lib library from \mysql\lib\opt. The stack traces were generated with the debug build, of course, so that's why the safemalloc is used. BOTH debug and release versions show this leak, though.

Still, we need to know which pointer is not released, because we tried lot's of different memory tracers which displayed wrong results.

The ones which we use are practically the only reliable ones, although even they fail sometimes, but not in this area of leak detection.