This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: problem catching C++ exceptions with gdb 4.18 on i686-pc-linux-gnu
- To: "Matthew D. Langston" <langston@SLAC.Stanford.EDU>
- Subject: Re: problem catching C++ exceptions with gdb 4.18 on i686-pc-linux-gnu
- From: Jim Blandy <jimb@cygnus.com>
- Date: 25 May 1999 22:04:47 -0500
- Cc: gdb@sourceware.cygnus.com
- References: <3744DA43.CF952461@SLAC.Stanford.EDU>
> I cannot seem to set a catchpoint on a C++ exception using gdb 4.18 and
> egcs 1.1.2 (AKA egcs-2.91.66) under x86 Linux (Pentium III, Linux
> 2.0.36, glibc 2.0.7, i686-pc-linux-gnu). According to "help catch":
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> Raised exceptions may be caught:
> catch throw - all exceptions, when thrown
> catch throw <exceptname> - a particular exception, when thrown
> catch catch - all exceptions, when caught
> catch catch <exceptname> - a particular exception, when caught
>
> [snip]
>
> C++ exceptions may be caught:
> catch throw - all exceptions, when thrown
> catch catch - all exceptions, when caught
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I think (I ought to be able to be authoritative here, bleah) that the
catch documentation is, plain and simple, lying. GDB can't catch
exceptions at all, except on certain architectures. I wish it could.