List:MySQL++« Previous MessageNext Message »
From:Michael Date:May 15 2009 1:12am
Subject:Segfault using thread_start
View as plain text  
Hello,

it seems like thread_start is not calling mysql_init implicitely, so
calls to mysqlpp::tgread_start result in a segfault (mysql++ 3.08 on
FreeBSD7.2).
Adding
mysqlpp::Connection() to the beginning of main works as a temporary fix,
but I think thread_start should somehow verify that mysql_(library)_init
is called at least once.
(in my case I put mysql_start and mysql_end in a general purpose
threading hook of the underlying framework)

cheers
Michael
Thread
Segfault using thread_startMichael15 May
  • Re: Segfault using thread_startWarren Young15 May
    • Re: Segfault using thread_startMichael15 May
      • Re: Segfault using thread_startWarren Young15 May
        • Re: Segfault using thread_startMichael15 May
        • Re: Segfault using thread_startWarren Young15 May
          • Re: Segfault using thread_startMichael15 May
            • Re: Segfault using thread_startWarren Young15 May
              • Re: Segfault using thread_startMichael15 May