From: Daniel Jacobowitz <drow@mvista.com>
To: Markus Werle <numerical.simulation@web.de>
Cc: gdb@sources.redhat.com
Subject: Re: catch throw -how?
Date: Tue, 28 Jan 2003 15:42:00 -0000 [thread overview]
Message-ID: <20030128154222.GA5561@nevyn.them.org> (raw)
In-Reply-To: <3E36A332.9648D75E@web.de>
On Tue, Jan 28, 2003 at 04:35:14PM +0100, Markus Werle wrote:
> Hi!
>
> Using gdb-5.1.1 I wanted to use the "catch" feature for C++ exceptions like this
>
> # gdb ./myprogram
> GNU gdb 5.1.1
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...
> (gdb) catch throw
> You can't do that without a process to debug.
> (gdb)
>
> 1. I do not understand the error message, please explain
> 2. Is this a bug resolved in gdb-5.3 or am I missing some information?
I don't think that "catch throw" works on any GNU/Linux target right
now. I've got it about half re-implemented for GCC 3.x in a scratch
directory right now but I don't know when I'm going to have time to
test it.
You can get just about the same effect in GCC 3.x by putting a
breakpoint on __cxa_throw. In 2.x I think it was __throw.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-28 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 15:35 Markus Werle
2003-01-28 15:42 ` Daniel Jacobowitz [this message]
2003-01-28 16:58 ` Markus Werle
2003-01-28 15:47 ` Bennett F. Dill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030128154222.GA5561@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=numerical.simulation@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox