From: "Alain Magloire" <alain@qnx.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: alain@qnx.com (Alain Magloire), gdb@sources.redhat.com
Subject: Re: catching exception in gdb
Date: Thu, 08 Jul 2004 23:18:00 -0000 [thread overview]
Message-ID: <200407082318.TAA23257@smtp.ott.qnx.com> (raw)
In-Reply-To: <20040708225744.GA4452@nevyn.them.org> from "Daniel Jacobowitz" at Jul 08, 2004 06:57:45 PM
>
> On Thu, Jul 08, 2004 at 06:43:17PM -0400, Alain Magloire wrote:
> >
> > Bonjour
> >
> > As suggested in the gdb doc, I was doing some hackish stuff in gdb-5.x to get catching exception working
> > in the eclipse CDT IDE. Using the C++ ABI and putting a "hidden" breakpoint in the "__cxa_xxx" functions.
> > So far so good, but once stop how to extract the class deep in the internal of the ABI.
> > I could not fine any ABI functions to do this nor walking through the arguments.
> >
> > Any suggestions ?
> >
> > gdb-6.x commands
> > catch throw <exceptname> - a particular exception, when thrown
> > catch catch <exceptname> - a particular exception, when caught
> > do not seem to work
> >
> > (gdb) catch catch Size
> > Junk at end of arguments.
>
> You can do it with the runtime type information, but I never got around
> to implementing it. It's fairly simple.
>
Sir ... You have my complete attention.
I like the sound of "it's fairly simple" ...
But I've learned the hard way, nothing is simple when dealing with gdb 8-).
So any good pointers ... been hamering away typecasting pointers to get the damn clazz name ... no go.
> "catch catch" and "catch throw" only work without arguments at the
> moment.
>
Noted.
prev parent reply other threads:[~2004-07-08 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 22:43 Alain Magloire
2004-07-08 22:58 ` Daniel Jacobowitz
2004-07-08 23:18 ` Alain Magloire [this message]
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=200407082318.TAA23257@smtp.ott.qnx.com \
--to=alain@qnx.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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