Warren,
Thanks for your suggestion. I hit google pretty hard to find any information
and found that different versions of gcc require different flags to handle
exceptions. I also found an interesting note, I believe from IBM-AIX release
note, mentioning that gcc3.3.X exception handling is not thread safe. Can
anyone comment on that? Did anyone try exception handling with
multi-threaded applications?
As far as your comment on the command line arguments, it appears that
starting from 2.95.X, exception handling options are not required on the
command line.
Alex
-----Original Message-----
From: Warren Young [mailto:mysqlpp@stripped]
Sent: Monday, February 14, 2005 10:11 AM
To: MySQL++ Mailing List
Subject: Re: mysql++1.7.28 core dumps on solaris
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.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsub=1
