My problem is resolved. I've upgraded the MySQL to version 5.5.38 from
5.0.95 and I've also done it to the mysql-devel package as well. The
5.5 devel pkg is called mysql55-mysql-devel for CentOS.
Now the valgrinds doesn't show any leaks whatsoever.
I thought I share my findings here and hopefully it will be helpful to someone.
On Tue, Jul 22, 2014 at 12:57 PM, Tamás Kása <nextimp@stripped>
> Thanks for the replies.
> The verbose output of the linker shows that these are the libraries it
> uses for compiling:
> I've check all of them with the file command and they are, in fact,
> 64-bit libraries.
> My initial action was to read the FAQ, but I came up short. Warrey
> Young, could you please elaborate your answer a little? I believe I'm
> doing everything that the FAQ suggests (calling
> Connection::thread_end() and mysql_library_end() at the end). Could
> you point me in the right direction?
> On Mon, Jul 21, 2014 at 10:14 PM, Chris Frey <cdfrey@stripped> wrote:
>> On Mon, Jul 21, 2014 at 04:11:41PM +0200, Tamás Kása wrote:
>>> The curious thing is that the test.cpp doesn't leak memory when
>>> compiled on a virtual system, which is exactly the same as the other
>>> mentioned above, except it is a 32 bit CentOS system, not 64 bit.
>> This is likely the biggest clue to the problem. I'm not sure
>> where the problem is, but you might check all supporting libraries,
>> making sure there are no 32/64 bit mismatches. Is the C mysql lib
>> 64bit too?
>> I suspect you're debugging a toolchain issue, not a code issue.
>> - Chris
>> MySQL++ Mailing List
>> For list archives: http://lists.mysql.com/plusplus
>> To unsubscribe: http://lists.mysql.com/plusplus