List:MySQL++« Previous MessageNext Message »
From:Calin Vaida Date:February 9 2005 3:05pm
Subject:Re: Connection close problem
View as plain text  
Hi,

I've installed Mysql 4.1.9 client in my box and I kept the
mysql++1.7.27 and again my program crashed with SEGFAULT in the very
same place.
Backtrace:
(gdb) bt
#0  0x401c4d32 in free_root () from /usr/local/lib/mysql/libmysqlclient.so.14
#1  0x401db8cc in free_old_query () from
/usr/local/lib/mysql/libmysqlclient.so.14
#2  0x401dc03a in mysql_close () from /usr/local/lib/mysql/libmysqlclient.so.14
#3  0x401dc01f in mysql_close () from /usr/local/lib/mysql/libmysqlclient.so.14
#4  0x4019225f in ~Connection (this=0xbfffea90) at connection.cpp:87
#5  0x0807b46b in ~MyDbConnect (this=0xbfffea90) at result.h:159
#6  0x08084f1d in IrisRepository::readTable (this=0x80d8d60,
table_id=0) at irisrepository.cpp:258
#7  0x0808c060 in IrisRepository::loadFromDB (this=0x80d8d60) at
irisrepository.cpp:79
....

But now, before the crash there was an error message: 
"glibc detected *** double free or corruption: 0xbfffe6ac ***"

Any idea? 

Thanks,
Calin

> Can you also try moving forward to a MySQL 4.1.x version?  There are
> some known changes in mysql_close functionality aroud 4.1.3.  See
> lib/connection.cc in MySQL++.
>
Thread
Connection close problemCalin Vaida7 Feb
  • Re: Connection close problemWarren Young7 Feb
    • Re: Connection close problemCalin Vaida7 Feb
      • Re: Connection close problemWarren Young7 Feb
        • Re: Connection close problemCalin Vaida8 Feb
          • Re: Connection close problemWarren Young8 Feb
            • Re: Connection close problemCalin Vaida9 Feb