This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR8554: New command to save breakpoints to a file

From: Sergio Durigan Junior <sergiodj at redhat dot com>
To: gdb-patches at sourceware dot org
Cc: Pedro Alves <pedro at codesourcery dot com>, tromey at redhat dot com
Date: Sat, 10 Apr 2010 01:10:02 -0300
Subject: Re: PR8554: New command to save breakpoints to a file
References: <201004090341.14389.pedro@codesourcery.com> <m3aatcob1g.fsf@fleche.redhat.com> <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

References:
- PR8554: New command to save breakpoints to a file
  - From: Pedro Alves
- Re: PR8554: New command to save breakpoints to a file
  - From: Tom Tromey
- Re: PR8554: New command to save breakpoints to a file
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]