I've been trying to isolate an obscure allocation problem. I'm embedding
xalan-c in an application that uses the Boehm garbage collector. Upgrading
to xalan-1.1 (and xerces-1.4) from xalan-1.0 exposed some problems,
manifesting as segfaults in malloc as well as some exceptions coming out
of the xalan and xerces libraries.
Since I don't have exception handlers in my code, the execution stack is
unwound up to main() from the throw. I tried setting a breakpoint on
__cp_push_exception and __cp_pop_exception to figure where the exception
was thrown, but the same thing happened. I noticed that
__cp_push_exception() __and cp_pop_exception() were at the same address,
which seems a little odd to me.
I would really appreciate any help in figuring out how to trap exceptions
with xalan in gcc.
-Alan Shieh
