From: Kevin Buettner Date: Wed, 5 Feb 2025 18:27:00 +0000 (-0700) Subject: Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple inferiors X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1290225912ff85331af5775b31be6217f42985a4;p=thirdparty%2Fbinutils-gdb.git Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple inferiors Reviewed-By: Eli Zaretskii Reviewed-By: Tom Tromey Approved-By: Andrew Burgess --- diff --git a/gdb/NEWS b/gdb/NEWS index 33d7af83d50..39a5f6683e3 100644 --- a/gdb/NEWS +++ b/gdb/NEWS @@ -24,6 +24,8 @@ * UST (static tracepoint) support from gdbserver has been removed. +* Linux checkpoint code has been updated to work with multiple inferiors. + * New commands maintenance check psymtabs diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index ff9fe298be3..b37266b708e 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -4322,18 +4322,36 @@ listed: @table @code @item Checkpoint ID +@item Active state indicator @item Process ID @item Code Address @item Source line, or label @end table +Checkpoint IDs will be displayed as either a non-negative integer or +in the form @var{i}.@var{n}, where @var{i} is the inferior number, a +positive integer, as shown by the command @code{info inferiors}, and +@var{n}, a non-negative integer, is the checkpoint number for that +inferior. The single non-negative integer form is used when +there is only one inferior. The @var{i}.@var{n} form is used when +there are multiple inferiors. + +The active state indicator is a single letter, either @samp{y} or +@samp{n}, indicating yes or no. Only one checkpoint per inferior may +be active at once. The active checkpoint in the current inferior is +also shown by a @samp{*} at the start of the line. Checkpoints whose +active state is @samp{n} can be switched to using the @code{restart} +command or deleted using the @code{delete checkpoint} command. + @kindex restart @var{checkpoint-id} @item restart @var{checkpoint-id} Restore the program state that was saved as checkpoint number @var{checkpoint-id}. All program variables, registers, stack frames etc.@: will be returned to the values that they had when the checkpoint was saved. In essence, gdb will ``wind back the clock'' to the point -in time when the checkpoint was saved. +in time when the checkpoint was saved. The checkpoint number +@var{checkpoint-id} is specified in the same form as that output by the +@code{info checkpoints} command. Note that breakpoints, @value{GDBN} variables, command history etc. are not affected by restoring a checkpoint. In general, a checkpoint