From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19062 invoked by alias); 4 Dec 2001 21:35:56 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 18813 invoked from network); 4 Dec 2001 21:35:47 -0000 Received: from unknown (HELO dc-mx08.cluster1.charter.net) (209.225.8.18) by sources.redhat.com with SMTP; 4 Dec 2001 21:35:47 -0000 Received: from [24.241.47.50] (HELO localhost) by dc-mx08.cluster1.charter.net (CommuniGate Pro SMTP 3.4.6) with ESMTP id 54300301; Tue, 04 Dec 2001 16:43:16 -0500 Received: from localhost ([127.0.0.1] helo=salmon.localnet) by localhost with esmtp (Exim 3.32 #1 (Debian)) id 16BNDs-0003N0-00; Tue, 04 Dec 2001 16:35:28 -0500 From: Klee Dienes Reply-To: Klee Dienes To: Eli Zaretskii cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] add 'save-breakpoints' command In-Reply-To: Your message of "Tue, 04 Dec 2001 21:21:56 +0200." <8582-Tue04Dec2001212156+0200-eliz@is.elta.co.il> References: <8582-Tue04Dec2001212156+0200-eliz@is.elta.co.il> Date: Tue, 04 Dec 2001 13:35:00 -0000 Message-Id: X-SW-Source: 2001-12/txt/msg00114.txt.bz2 > 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