List:MySQL++« Previous MessageNext Message »
From:Chris Gagnon Date:February 25 2005 4:25am
Subject:Follow up to "seg fault as soon as i try to get a Result Set"
View as plain text  
Sorry, couldn't actually reply to that thread.

 

I did a backtrace on the seg fault which gives me:

Program received signal SIGSEGV, Segmentation fault.

0x280b6c8c in MysqlConnection::store () from /usr/local/lib/libsqlplus.so.1

(gdb) bt

#0  0x280b6c8c in MysqlConnection::store () from
/usr/local/lib/libsqlplus.so.1

#1  0x805a25d in MysqlConnection::store ()

    at /usr/include/g++/stl_construct.h:43

#2  0x8058543 in MysqlQuery::store () at /usr/include/g++/stl_construct.h:43

#3  0x8057149 in MysqlQuery::store () at /usr/include/g++/stl_construct.h:43

#4  0x80550f4 in EOSUniverse::LoadUniverse ()

    at /usr/include/g++/stl_construct.h:43

#5  0x804e9f1 in EOSServer::Initialize ()

#6  0x804e634 in EOSServer::run ()

#7  0x80602d1 in main () at main.cpp:144

 

As for some of the comments I changed the creation to be on the stack, and
removed the multi level exception handling which didn't seen to fix the
problem.

 

On another note I wrote a test program that retrieves a result set no
problem.

 

If needed I can post my new code. to give an idea of what I have now

-Chris


Thread
Follow up to "seg fault as soon as i try to get a Result Set"Chris Gagnon25 Feb
Re: Follow up to "seg fault as soon as i try to get a Result Set"Warren Young25 Feb
  • RE: Follow up to "seg fault as soon as i try to get a Result Set"Chris Gagnon27 Feb
Re: Follow up to "seg fault as soon as i try to get a Result Set"Warren Young1 Mar
Re: Follow up to "seg fault as soon as i try to get a Result Set"Warren Young1 Mar