From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [0/2] more OO, Ada exception catchpoints: intro
Date: Wed, 22 Jun 2011 17:24:00 -0000 [thread overview]
Message-ID: <m31uyl6aq1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201106221420.08780.pedro@codesourcery.com> (Pedro Alves's message of "Wed, 22 Jun 2011 14:20:08 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> (serving as proof/excuse for me to add a few more bits to
Pedro> breakpoint_ops and export a few functions from breakpoint.c :-)
Pedro> ).
As far as I'm concerned, you don't need an excuse to do this.
I think it would be best if all breakpoints had to use breakpoint_ops
and there were no switches in breakpoint.c, just indirect calls.
Tom
next prev parent reply other threads:[~2011-06-22 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 13:20 Pedro Alves
2011-06-22 16:35 ` Joel Brobecker
2011-06-22 17:56 ` Pedro Alves
2011-06-22 17:24 ` Tom Tromey [this message]
2011-06-22 18:14 ` Pedro Alves
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=m31uyl6aq1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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