>From what I can tell, __cp_push_exception is the equivalent of
__raise_exception in x86.
On Thu, 31 May 2001 [EMAIL PROTECTED] wrote:
> Have you looked at 5.1.3 in the GDB 5.0 manual?
> http://sunsite.ualberta.ca/Documentation/Gnu/gdb-5.0/html_node/gdb_30.html#S
> EC30
>
> Zartaj
>
> > -----Original Message-----
> > From: Alan C Shieh [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 31, 2001 4:38 AM
> > To: [EMAIL PROTECTED]
> > Subject: Trapping exceptions in gdb on i386 Linux
> >
> >
> > 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
> >
>
