[PATCH v4 4/4] Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple inferiors

[Kevin Buettner <kevinb@redhat.com>]

---
 gdb/NEWS            |  2 ++
 gdb/doc/gdb.texinfo | 23 ++++++++++++++++++++++-
 2 files changed, 24 insertions(+), 1 deletion(-)

diff --git a/gdb/NEWS b/gdb/NEWS
index 47677cb773a..380a204e5a2 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -13,6 +13,8 @@
   This may cause breakage when using an incompatible libc, like uclibc or
   newlib, or an older glibc.
 
+* Linux checkpoint code has been updated to work with multiple inferiors.
+
 *** Changes in GDB 15
 
 * The MPX commands "show/set mpx bound" have been deprecated, as Intel
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 86cd420832a..01d90ec0934 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4316,18 +4316,39 @@ listed:
 
 @table @code
 @item Checkpoint ID
+@item Status
 @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
+checkpoint(s) have been placed for a single inferior.  The
+@var{I}.@var{N} form is used when checkpoints have been created for
+multiple inferiors.
+
+Status information consists of the letters @code{A} and @code{R}. 
+@code{A} indicates an active processes in the checkpoint list; this is
+one which @value{GDBN} is currently debugging.  @code{R} indicates a
+running process; this status letter can only appear when @value{GDBN}
+is running in non-stop mode.  If neither @code{A} or @code{R} are present,
+this indicates a checkpoint which 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
-- 
2.45.2