From: Pedro Alves <pedro@palves.net>
To: Markus Metzger <markus.t.metzger@intel.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] gdb, btrace: infrun fixes
Date: Wed, 3 Nov 2021 18:52:15 +0000 [thread overview]
Message-ID: <0be6bfa9-83a9-fd7d-e218-58b331ab6569@palves.net> (raw)
In-Reply-To: <20210316093501.936148-1-markus.t.metzger@intel.com>
Hi Markus,
I ran the tests included in the series against pristine / unfixed GDB, and got:
Using /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/stepn.exp ...
Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/implicit-stop-replaying.exp ...
FAIL: gdb.btrace/implicit-stop-replaying.exp: thread apply 1 info record
Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/step-hang.exp ...
FAIL: gdb.btrace/step-hang.exp: continue until exit (timeout)
Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/cont-hang.exp ...
FAIL: gdb.btrace/cont-hang.exp: continue until exit (timeout)
Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/multi-thread-break-hang.exp ...
FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.2 (timeout)
FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.3 (timeout)
The curious thing is that stepn.exp doesn't fail, it passes anyhow. Is that expected?
Also, I diffed gdb.log before/after patch, and noticed a difference. GDB no longer prints the current
location:
No more reverse-execution history.
-main () at /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/record_goto.c:50
50 return 0; /* main.3 */
Is this expected?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2021-11-03 18:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:34 Markus Metzger
2021-03-16 9:34 ` [PATCH 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger
2021-11-03 13:11 ` Pedro Alves
2021-11-22 17:23 ` Metzger, Markus T
2021-03-16 9:34 ` [PATCH 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger
2021-11-03 14:51 ` Pedro Alves
2021-11-22 17:23 ` Metzger, Markus T
2021-03-16 9:35 ` [PATCH 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger
2021-11-03 14:58 ` Pedro Alves
2021-03-16 9:35 ` [PATCH 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger
2021-11-03 18:43 ` Pedro Alves
2021-11-22 17:23 ` Metzger, Markus T
2021-04-13 11:43 ` [PATCH 0/4] gdb, btrace: infrun fixes Metzger, Markus T
2021-05-26 2:49 ` Simon Marchi
2021-06-08 9:05 ` Metzger, Markus T
2021-07-28 6:41 ` Metzger, Markus T
2021-09-21 9:45 ` Metzger, Markus T
2021-11-03 18:52 ` Pedro Alves [this message]
2021-11-23 11:33 ` Metzger, Markus T
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=0be6bfa9-83a9-fd7d-e218-58b331ab6569@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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).