On Wed, 2003-07-16 at 13:11, Egbert Eich wrote:
> We have a bug report at
>
> http://bugs.xfree86.org/show_bug.cgi?id=503
>
> that suggests that when building libraries with callbacks using gcc
> the option -fexeptions should be used. It enables C++ programs
> to catch the exceptions.
> I've talked to a gcc expert and he says that using this option is
> sane. It adds unwind information and on some targets it supresses
> a few optimizations that break unwinding, however these optimizations
> are no big deal.
> In statically linked binaries the exception tables should
> automatically be removed if the binary does not use them.
Is this useful if the libraries don't properly handle exceptions
being thrown through them?
I'd really suspect that most/all places where there are callbacks
in the X libraries they will leak memory / corrupt state / otherwise
misbehave if you throw an exception from a callback and catch it in
the surrounding code.
Regards,
Owen
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
