From: Daniel Jacobowitz <drow@mvista.com>
To: Alain Magloire <alain@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: Catchpoint in GDB/MI
Date: Tue, 06 May 2003 19:52:00 -0000 [thread overview]
Message-ID: <20030506195208.GA15526@nevyn.them.org> (raw)
In-Reply-To: <200305061946.PAA03660@node1.ott.qnx.com>
On Tue, May 06, 2003 at 03:46:40PM -0400, Alain Magloire wrote:
> >
> > On Tue, May 06, 2003 at 12:12:10PM -0400, Alain Magloire wrote:
> > > >
> > > > On Tue, May 06, 2003 at 11:15:50AM -0400, Alain Magloire wrote:
> > > > > >
> > > > > > On Tue, May 06, 2003 at 10:50:47AM -0400, Alain Magloire wrote:
> > > > > > > Bonjour
> > > > > > >
> > > > > > > Anyone working on putting catchpoints in GDB/MI.
> > > > > > > If yes what is the semantics.
> > > > > > > If no what is the best semantic? Completely OOB:
> > > > > > >
> > > > > > > -catch load
> > > > > > > ^done
> > > > > > > ...
> > > > > > >
> > > > > > > *stop,reason="shared-loaded",shared="libm.so"
> > > > > >
> > > > > > Do we even have any targets besides HP/UX where shared library
> > > > > > catchpoints _work_?
> > > > >
> > > > > Probably none, in the gdb source tree. For example, catching exceptions
> > > > > is probably compiler dependent 8-( .. I think. Do remember Daniel Berlin
> > > > > proposing a scheme for gcc long long time ago, could not retrace the email
> > > > > though ... darn!
> > > >
> > > > I've actually added catchpoints for exceptions back; but they'll just
> > > > show up as breakpoints for now. If we want them to show up differently
> > > > someone's going to have to work out (both CLI and MI) what they should
> > > > look like.
> > > >
> > >
> > > Details please? 8-)
> > >
> > > Do you mean setting breakpoint on some special function used to throw
> > > exception __raise_exception(..)?
> > >
> > > How does it work ?
> >
> > Yes. It's __cxa_throw and __cxa_begin_catch; I only implemented them
> > for the GCC 3.x (i.e. multivendor) ABI. You can find the patch in the
> > archives if you want to know more :)
> >
>
> Are you refering to this:
> http://sources.redhat.com/ml/gdb/2002-07/msg00191.html
>
> Very informative, thanks.
>
> Reading your exchange, I probably can implement your scheme whithout
> having to change gdb; setting the breakpoint in __cxa_throw and examining
> the arguments.
>
> It seems straightforward enough, so why not put it in gdb? Unless
> of course I do not grasp the entire complexity of the problem 8-)
> True it is compiler specific unless the cxxabi becomes more widespread
> but at least a start.
No, I was referring to the message a few weeks ago where I checked in
support for "catch catch". It doesn't yet parse a type to catch but
that is easy to add once the FETCH_POINTER_ARGUMENT method is
available.
Alain, something is wrong with your mailer; I'm getting two copies with
different Message-Id's of everything you send me.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-06 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 14:50 Alain Magloire
2003-05-06 14:59 ` Daniel Jacobowitz
2003-05-06 15:16 ` Alain Magloire
[not found] ` <200305061516.LAA05153@node1.ott.qnx.com>
2003-05-06 15:31 ` Daniel Jacobowitz
2003-05-06 16:12 ` Alain Magloire
[not found] ` <200305061612.MAA09299@node1.ott.qnx.com>
2003-05-06 16:45 ` Daniel Jacobowitz
2003-05-06 19:46 ` Alain Magloire
[not found] ` <200305061946.PAA03660@node1.ott.qnx.com>
2003-05-06 19:52 ` Daniel Jacobowitz [this message]
2003-05-06 21:21 ` Alain Magloire
2003-05-06 21:28 ` Daniel Jacobowitz
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=20030506195208.GA15526@nevyn.them.org \
--to=drow@mvista.com \
--cc=alain@qnx.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).