Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Klee Dienes <klee@apple.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] add 'save-breakpoints' command
Date: Tue, 04 Dec 2001 13:35:00 -0000	[thread overview]
Message-ID: <E16BNDs-0003N0-00@localhost> (raw)
In-Reply-To: Your message of "Tue, 04 Dec 2001 21:21:56 +0200." <8582-Tue04Dec2001212156+0200-eliz@is.elta.co.il>


> Thanks!  Please consider writing up some minimal docs for this
> functionality, for the gdb.texinfo manual.

Whoops.  How about this:

--- cygnus.pristine/src/gdb/doc/gdb.texinfo     Fri Nov 30 19:27:53 2001
+++ cygnus.patched/src/gdb/doc/gdb.texinfo      Tue Dec  4 16:27:02 2001
@@ -2335,6 +2335,7 @@
 * Set Catchpoints::             Setting catchpoints
 * Delete Breaks::               Deleting breakpoints
 * Disabling::                   Disabling breakpoints
+* Saving::                      Saving breakpoints
 * Conditions::                  Break conditions
 * Break Commands::              Breakpoint command lists
 * Breakpoint Menus::            Breakpoint menus
@@ -2941,6 +2942,22 @@
 breakpoint of its own, but it does not change the state of your other
 breakpoints; see @ref{Continuing and Stepping, ,Continuing and
 stepping}.)
+
+@node Saving
+@subsection Saving breakpoints
+@cindex save breakpoints for future sessions
+
+Sometimes, it can be convenient to save the current set of breakpoints
+for use in a future debugging session:
+
+@table @code
+@kindex save-breakpoints
+@item save-breakpoints
+Save all current breakpoint definitions, together with their
+ignore-counts and command scripts, into the file @file{@var{filename}}.
+To read the saved breakpoint definitions, use the @code{source} command
+(@pxref{Command Files}).
+@end table


  reply	other threads:[~2001-12-04 21:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 10:21 Klee Dienes
2001-12-04 10:26 ` Daniel Jacobowitz
2001-12-04 10:44   ` Klee Dienes
2001-12-05 14:06     ` Tom Tromey
2001-12-04 11:22 ` Eli Zaretskii
2001-12-04 13:35   ` Klee Dienes [this message]
2001-12-05  0:25     ` Eli Zaretskii
2001-12-04 14:48 ` Michael Snyder
2001-12-04 21:11   ` Klee Dienes
2001-12-11  0:28   ` Klee Dienes
2001-12-11  3:55     ` Eli Zaretskii
2001-12-11  8:35       ` Klee Dienes
2001-12-11  9:09         ` Eli Zaretskii
2001-12-11 13:23           ` Klee Dienes
2001-12-12  0:32             ` Eli Zaretskii
2001-12-14 12:45               ` Klee Dienes
2001-12-14 12:50                 ` Daniel Jacobowitz
2001-12-18  1:42                   ` Klee Dienes
     [not found] <1007594419.30359.ezmlm@sources.redhat.com>
2001-12-05 17:39 ` Jim Ingham

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=E16BNDs-0003N0-00@localhost \
    --to=klee@apple.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@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