public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v3] gdb: add 'maintenance print record-instruction' command
Date: Tue, 3 Jan 2023 10:00:04 +0100	[thread overview]
Message-ID: <fe848d43-3b98-3e2f-8d2e-fd4ac141709d@redhat.com> (raw)
In-Reply-To: <CAJVr-EOt3UoTE_Q4e_2o2gfdVG9-2QiWAp7L4XZ66=VY7x7BdA@mail.gmail.com>

On 02/01/2023 16:37, Alexandra Petlanova Hajkova wrote:
>
>     +# This file is part of the GDB testsuite.  it tests the
>     functionality of
>     +# the maintenance print record-instruction command, but does not
>     check the
>     +# syntax, only if the command finds or fails to find recorded
>     history.
>     +
>     +if ![supports_reverse] {
>     +    return
>     +}
>     +
>
>
> I think this patch is good to go in general.
>  But it might be nice to add a small summary about how the test works 
> as a comment at the beginning of the test?
>
I see. I've expanded that starting comment to the following:

# This file is part of the GDB testsuite.  It tests the functionality of
# the maintenance print record-instruction command, but does not check the
# syntax, only if the command finds or fails to find recorded history.
# This is done by putting the inferior in mulpitle states with and without
# history to be printed, then checking if GDB is able to print an
# instruction or not.
# To identify if GDB has printed an instruction, we can see if some
# change is printed, since any instruction must have at least a change
# to the PC.

What do you think?

-- 
Cheers,
Bruno

> Regards,
> Alexandra



  reply	other threads:[~2023-01-03  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 15:43 Bruno Larsen
2023-01-02 15:37 ` Alexandra Petlanova Hajkova
2023-01-03  9:00   ` Bruno Larsen [this message]
2023-01-02 16:26 ` Lancelot SIX
2023-01-02 16:56   ` Bruno Larsen
2023-01-03 16:10     ` Lancelot SIX
2023-01-03 17:04 ` Tom Tromey
2023-01-04 10:30 ` Bruno Larsen

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=fe848d43-3b98-3e2f-8d2e-fd4ac141709d@redhat.com \
    --to=blarsen@redhat.com \
    --cc=ahajkova@redhat.com \
    --cc=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).