List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:February 14 2005 3:10pm
Subject:Re: mysql++1.7.28 core dumps on solaris
View as plain text  
Alex Vishnev wrote:

> #0  0xff09c4ac in _libc_kill () from /lib/libc.so.1
> #1  0xff035a84 in abort () from /lib/libc.so.1
> #2  0xff161acc in __cxxabiv1::__terminate (handler=0xff03597c <abort>) at
> ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47

This looks like an uncaught exception to me.  MySQL++ throws exceptions 
to flag errors, and somehow the exception isn't being caught.  In the 
past, I've seen many error reports on Solaris regarding exception 
handling.  I don't know that this means that it is broken, but it may be 
that it isn't obvious how to set it up properly.  For instance, perhaps 
you need to pass special flags to the compiler to get it to work right. 
  Just a guess.
Thread
mysql++1.7.28 core dumps on solarisAlex Vishnev12 Feb
  • Re: mysql++1.7.28 core dumps on solarisChris Frey12 Feb
    • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev12 Feb
      • Re: mysql++1.7.28 core dumps on solarisChris Frey13 Feb
        • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev14 Feb
          • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
    • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
  • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
    • RE: mysql++1.7.28 core dumps on solarisAlex Vishnev14 Feb
      • Re: mysql++1.7.28 core dumps on solarisWarren Young14 Feb
        • mysql++1.7.28 thread safetyAlex Vishnev14 Feb
          • Re: mysql++1.7.28 thread safetyEarl Miles14 Feb
            • Re: mysql++1.7.28 thread safetyWarren Young14 Feb
              • Re: mysql++1.7.28 thread safetyEarl Miles14 Feb
              • RE: mysql++1.7.28 thread safetyAlex Vishnev15 Feb
                • Re: mysql++1.7.28 thread safetyWarren Young16 Feb