Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex Chronopoulos <achronop@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5] Change message when reaching end of reverse history.
Date: Tue, 09 Jul 2024 05:25:16 +0300	[thread overview]
Message-ID: <86ttgzz4hf.fsf@gnu.org> (raw)
In-Reply-To: <20240708192730.264313-1-achronop@gmail.com> (message from Alex Chronopoulos on Mon, 8 Jul 2024 21:27:30 +0200)

> From: Alex Chronopoulos <achronop@gmail.com>
> Cc: Alex Chronopoulos <achronop@gmail.com>
> Date: Mon,  8 Jul 2024 21:27:30 +0200
> 
> In a record session, when we move backward, GDB switches from normal
> execution to simulation. Moving forward again, the emulation continues
> until the end of the reverse history. When the end is reached, the
> execution stops, and a warning message is shown. This message has been
> modified to indicate that the forward emulation has reached the end, but
> the execution can continue as normal, and the recording will also continue.
> 
> Before this patch, the warning message shown in that case was the same as
> in the reverse case. This meant that when the end of history was reached in
> either backward or forward emulation, the same message was displayed:
> 
> "No more reverse-execution history."
> 
> This message has changed for these two cases. Backward emulation:
> 
> "Reached end of recorded history; stopping.
> Backward execution from here not possible."
> 
> Forward emulation:
> 
> "Reached end of recorded history; stopping.
> Following forward execution will be added to history."
> 
> The reason for this change is that the initial message was deceiving, for
> the forward case, making the user believe that forward debugging could not
> continue.
> 
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31224
> ---
>  gdb/NEWS                                      |  5 +++
>  gdb/infrun.c                                  |  9 +++++-
>  gdb/testsuite/gdb.btrace/non-stop.exp         | 32 ++++++++++++-------
>  gdb/testsuite/gdb.reverse/break-precsave.exp  |  6 ++--
>  gdb/testsuite/gdb.reverse/break-reverse.exp   |  4 +--
>  .../gdb.reverse/machinestate-precsave.exp     |  2 +-
>  gdb/testsuite/gdb.reverse/sigall-precsave.exp |  2 +-
>  7 files changed, 41 insertions(+), 19 deletions(-)

I'm not sure this change warrants a NEWS entry, but if it does, the
NEWS part is approved.  Thanks.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2024-07-09  2:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 19:27 Alex Chronopoulos
2024-07-09  2:25 ` Eli Zaretskii [this message]
2024-07-09  6:24 ` Metzger, Markus T
2024-08-02 16:36   ` Alex Chronopoulos

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=86ttgzz4hf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=achronop@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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