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: Pedro Alves <pedro at codesourcery dot com>
To: Michael Snyder <msnyder at vmware dot com>
Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, "tromey at redhat dot com" <tromey at redhat dot com>
Date: Fri, 16 Apr 2010 00:20:11 +0100
Subject: Re: PR8554: New command to save breakpoints to a file
References: <201004090341.14389.pedro@codesourcery.com> <4BC79A0F.9090406@vmware.com> <4BC79DC3.7070308@vmware.com>

On Friday 16 April 2010 00:14:11, Michael Snyder wrote:
> Also, it doesn't seem right to me that "save tracepoints" will ignore
> breakpoints, but "save breakpoints" doesn't ignore tracepoints (but
> rather saves them both).
> 
> Since you have this filter mechanism in place already, why don't you
> arrange to have "save breakpoints" save only breakpoints?

Because "info breakpoints" also lists all kinds of breakpoints
(real-breakpoints, watchpoints, tracepoints, catchpoints), and
"info tracepoints" only lists tracepoints.  Please refer to
last January's discution about "actionpoints" over at gdb@.

-- 
Pedro Alves

References:
- PR8554: New command to save breakpoints to a file
  - From: Pedro Alves
- Re: PR8554: New command to save breakpoints to a file
  - From: Michael Snyder
- Re: PR8554: New command to save breakpoints to a file
  - From: Michael Snyder

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