List:MySQL++« Previous MessageNext Message »
From:Calin Vaida Date:February 7 2005 12:49pm
Subject:Connection close problem
View as plain text  
Hi everyone,

I have a problem with a project of mine that work perfectly on my old
OS (Suse 8.1) with a compiled version of mysql-3.23.58 and
mysql++1.7.17, but now I have changed my OS with the Suse 9.2 that has
its own  mysql 4.0.21 version and I have compiled the mysql++1.7.27
and it seems to be a problem because now my project end with a
SEGFAULT.  Here I have attached a backtrace of my problem:

(gdb) bt
#0  0x401c1314 in free_root () from /usr/lib/mysql/libmysqlclient.so.12
#1  0x401b8c3e in free_old_query () from /usr/lib/mysql/libmysqlclient.so.12
#2  0x401bbf8d in mysql_close () from /usr/lib/mysql/libmysqlclient.so.12
#3  0x401bbf4e in mysql_close () from /usr/lib/mysql/libmysqlclient.so.12
#4  0x4019225f in ~Connection (this=0xbfffee00) at connection.cpp:87
#5  0x0807b46b in ~MyDbConnect (this=0xbfffee00) 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

So I guess that is something with the destruction process of the mysql
connection, but what is very strange is that the examples from mysql++
are going without problems.

If someone have any clue about it please let me know.

Many thanks

Calin.
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