Re: [Mysqlcppapi-main] memory leaks

[Radoslaw G. <rga...@ay...>]

Hi,

My previous post concerned memory leaks problems.

I used the libc mtrace() function for more detailed study of the problem =
and=20
it appeared that it had been caused mainly by the "mysqlclient" library f=
rom=20
"mysql" package. There were also some problems with strstring class but a=
s I=20
checked, the latest version of "mysqlcppapi" uses the newest solution=20
(stringstream) which should not cause any problems with memory allocation=
=2E

So, according to the results of my "detailed" studies, I have download th=
e=20
latest version of the mysql package (4.0.12-0) - and after all recompilat=
ions=20
there are no problems with memory allocations inside it BUT, unfortunatel=
y=20
the new problems arises with the mysqlcppapi library:

The output from mtrace() (the memory which was allocated and never freed)=
:  =20
1) /usr/lib/libmysqlcppapi-1.9-1.9.so.3:(my_malloc+0x1f)[0x402c83bf] +=20
0x8061ad8 0x40
2)  /usr/lib/libmysqlcppapi-1.9-1.9.so.3:(my_once_alloc+0x5e)[0x402cd0ae]=
 +=20
0x80644c8 0xff8

 Please let me know in case of the need of any additional information.

current packages versions:
MySQL           : 4.0.12-0
mysqlcppapi  : 1.9.2-0

all packages were recompiled on my system:=20
        Linux Suse 8.0 (upgraded)
        glibc-2.2.5-158
        gcc-2.95.3-216


 Any help appreciated.


ps. the problem with a segmentation fault error has not appeared so far w=
ith=20
the new mysql library,


--=20
    //=09Radoslaw Garbacz
    //  aycan Digitalsysteme GmbH
    //  Innere Aumuehlstrasse 5
    //  97076 Wuerzburg
    //  phone: +49 931-2 70 40 9-0
    //  fax:   +49 931-2 70 40 9-1
    //  http://www.aycan.de