From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@codesourcery.com>, tromey@redhat.com
Subject: Re: PR8554: New command to save breakpoints to a file
Date: Sat, 10 Apr 2010 04:10:00 -0000 [thread overview]
Message-ID: <201004100110.02838.sergiodj@redhat.com> (raw)
In-Reply-To: <201004091823.31659.pedro@codesourcery.com>
On Friday 09 April 2010 14:23:31, Pedro Alves wrote:
> > Pedro> The new breakpoint_ops->print_recreate method implementation for
> > Pedro> all catchpoints is always mostly a simplified version of
> > Pedro> breakpoint_ops->print_mention method.
> >
> > Could you enlighten me on a historical (?) point? Why is it that some
> > kinds of breakpoints have methods like this and some do not? Is this an
> > incomplete transition, or an intentional design choice?
>
> I think the former. breakpoint_ops was added initialy for some
> catchpoints in 2003. I wasn't around then.
FWIW, Joel has kindly made fork/vfork catchpoints use the breakpoint_ops, but
this was only in 2008.
http://sourceware.org/ml/gdb-patches/2008-10/msg00148.html
--
Sergio
next prev parent reply other threads:[~2010-04-10 4:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 2:41 Pedro Alves
2010-04-09 16:17 ` Tom Tromey
2010-04-09 17:23 ` Pedro Alves
2010-04-10 4:10 ` Sergio Durigan Junior [this message]
2010-04-12 18:15 ` Pedro Alves
2010-04-15 17:52 ` Michael Snyder
2010-04-15 18:27 ` Pedro Alves
2010-04-15 18:46 ` Michael Snyder
2010-04-15 18:53 ` Pedro Alves
2010-04-15 18:58 ` Michael Snyder
2010-04-15 19:58 ` Pedro Alves
2010-04-15 22:49 ` Michael Snyder
2010-04-15 22:52 ` Michael Snyder
2010-04-15 22:58 ` Michael Snyder
2010-04-15 23:05 ` Pedro Alves
2010-04-15 23:15 ` Michael Snyder
2010-04-15 23:25 ` Pedro Alves
2010-05-05 8:28 ` Hui Zhu
2010-04-15 23:14 ` Michael Snyder
2010-04-15 23:20 ` Pedro Alves
2010-04-15 23:01 ` Pedro Alves
2010-04-15 18:59 ` Stan Shebs
2010-04-15 19:10 ` 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=201004100110.02838.sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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