From: Guinevere Larsen <blarsen@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Guinevere Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4 0/4] Many fixes to gdb.reverse tests when testing
Date: Thu, 24 Aug 2023 18:06:30 +0200 [thread overview]
Message-ID: <af3b3c76-745c-294c-2fc5-9b159a7bc66a@redhat.com> (raw)
In-Reply-To: <87fs49veg0.fsf@tromey.com>
On 23/08/2023 19:47, Tom Tromey wrote:
>>>>>> Guinevere Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
>> This patch series applies multiple simple fixes to tests in the
>> gdb.reverse subdirectory. Changes were tested with the base
>> configuration in x86_64, both with clang and gcc, and no regressions
>> were found.
>> With these changes, there are only 10 unexpected failures extra when
>> running the subdirectory with clang, all from finish-reverse-next.exp,
>> and all relating to the issues that Carl Love has been trying to solve
>> with reverse stepping in contiguous ranges.
> Thank you.
>
> Approved-By: Tom Tromey <tom@tromey.com>
Thanks, pushed!
--
Cheers,
Guinevere Larsen
She/Her/Hers
prev parent reply other threads:[~2023-08-24 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 10:43 Guinevere Larsen
2023-08-23 10:43 ` [PATCH v4 1/4] gdb/testsuite: Fix many errors in gdb.reverse with clang Guinevere Larsen
2023-08-23 10:43 ` [PATCH v4 2/4] gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang Guinevere Larsen
2023-08-23 10:43 ` [PATCH v4 3/4] gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang Guinevere Larsen
2023-08-23 10:43 ` [PATCH v4 4/4] gdb/testsuite: Multiple improvements for gdb.reverse/insn-reverse.exp Guinevere Larsen
2023-08-23 17:47 ` [PATCH v4 0/4] Many fixes to gdb.reverse tests when testing Tom Tromey
2023-08-24 16:06 ` Guinevere Larsen [this message]
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=af3b3c76-745c-294c-2fc5-9b159a7bc66a@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).