RE: C++ exceptions don't work from Cygwin DLLs?

[Danny Smith]

 --- Robert Collins <address@hidden> wrote: > Danny, I hope you
don't object to being copied in...
> 
> > -----Original Message-----
> > From: Charles Wilson [mailto:address@hidden 
> > Sent: Saturday, May 11, 2002 7:49 AM
> > To: Bob Friesenhahn
> > Cc: address@hidden; Robert Collins
> > Subject: Re: C++ exceptions don't work from Cygwin DLLs?
> > 
> > 
> > Bob Friesenhahn wrote:
> > 
> > > I am attempting to get ImageMagick to work properly using 
> > Cygwin DLLs. 
> > > The C++ component is built as a DLL using the binutils auto-import 
> > > feature and CVS libtool.  The library works fine with the glaring 
> > > exception that any C++ exception thrown from the library causes an 
> > > immediate core dump.  I have verified that C++ exceptions 
> > do work if 
> > > they are not thrown from a DLL, and the library passes all tests 
> > > (including C++ exceptions) if it is built as a static library.
> > > 
> > > Do you believe that C++ exceptions should be working with 
> > Cygwin DLLs?
> > 

Known problem which will not be solved until the exception handling mechansim
of libgcc.a lives in a .dll    What happens is that there are too copies of the

exception handling code: One in the dll and one in the app.   The one in dll is
there because of the problem with no-undefined synbols when building the dll.  
When the dll throws an exception it expects to catch it in its own  space. It
doesn't (because the catch is in the app space) so the uncaught exception
causes an abort.  That was my excuse when I played shortstop anyway.

Danny

http://messenger.yahoo.com.au - Yahoo! Messenger
- A great way to communicate long-distance for FREE!