From: Carl Love <cel@us.ibm.com>
To: Luis Machado <luis.machado@linaro.org>, gdb@sourceware.org
Cc: Rogerio Alves <rogealve@br.ibm.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: RE: GDB reverse execution question
Date: Tue, 06 Jul 2021 13:53:31 -0700 [thread overview]
Message-ID: <19999a766ed0a18c95619495aa4cfc4a4c5253ca.camel@us.ibm.com> (raw)
In-Reply-To: <0581aed7-5fbb-4764-d6fa-ac6a0573044e@linaro.org>
On Mon, 2021-07-05 at 08:26 -0300, Luis Machado wrote:
> Does the following fix the problem for you?
>
> https://sourceware.org/pipermail/gdb-patches/2021-February/175678.html
>
The patch does fix a number of the reverse regression test failures.
However, the specific test that I am looking at, finish-reverse.exp, is
not fixed. Here is the list of failures with and without your fix:
err file name no patch louise patch
gdb.reverse/finish-reverse-bkpt.exp 2 2
gdb.reverse/finish-reverse.exp 11 11
gdb.reverse/fstatat-reverse.exp 1 1
gdb.reverse/next-reverse-bkpt-over-sr.exp 2 2
gdb.reverse/solib-precsave.exp 17 0
gdb.reverse/solib-reverse.exp 17 0
gdb.reverse/step-precsave.exp 7 0
gdb.reverse/step-reverse.exp 7 0
gdb.reverse/until-precsave.exp 2 2
gdb.reverse/until-reverse.exp 1 1
I will look a bit more into what your patch is doing and see if I can
understand what is going on in the finish-reverse.exp test with regards
to your patch. Thanks for the help.
Carl
next prev parent reply other threads:[~2021-07-06 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 18:38 Carl Love
2021-07-05 11:26 ` Luis Machado
2021-07-06 20:53 ` Carl Love [this message]
2021-07-06 21:08 ` Carl Love
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=19999a766ed0a18c95619495aa4cfc4a4c5253ca.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=rogealve@br.ibm.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).