From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "pedro@palves.net" <pedro@palves.net>
Subject: RE: [PATCH v5 0/4] PR gdb/31353
Date: Mon, 21 Oct 2024 09:46:11 +0000 [thread overview]
Message-ID: <BN0PR11MB5757A3B29218DB0CF421FBF6DE432@BN0PR11MB5757.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87ldyhyg1h.fsf@redhat.com>
Hello Andrew,
>I built this series off current master, ran these tests and saw 6
>unexpected failures:
>
> FAIL: gdb.btrace/stepn.exp: stepi: stepi 5
> FAIL: gdb.btrace/stepn.exp: step: step 5
> FAIL: gdb.btrace/stepn.exp: next: next 5
> FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.1
> FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.2
> FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.3
Those fails are caused by some rewording of the end-of-history message.
I fixed them on the user branch but have not sent another version of the
patch series. I noted this in the wrong patch series (the one for gdb/19340).
I'll send an update.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2024-10-21 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:46 Markus Metzger
2024-04-10 7:46 ` [PATCH v5 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger
2024-04-10 7:46 ` [PATCH v5 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger
2024-04-10 7:46 ` [PATCH v5 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger
2024-04-10 7:46 ` [PATCH v5 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger
2024-04-12 19:50 ` Guinevere Larsen
2024-04-15 9:03 ` Metzger, Markus T
2024-04-15 12:44 ` Guinevere Larsen
2024-05-03 5:26 ` [PING] [PATCH v5 0/4] PR gdb/31353 Metzger, Markus T
2024-06-07 5:06 ` [PING v2] " Metzger, Markus T
2024-06-27 19:12 ` Guinevere Larsen
2024-09-13 10:43 ` [PING v3] " Metzger, Markus T
2024-10-09 14:10 ` [PING v4] " Metzger, Markus T
2024-10-21 8:45 ` Andrew Burgess
2024-10-21 9:13 ` Andrew Burgess
2024-10-21 9:46 ` Metzger, Markus T [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=BN0PR11MB5757A3B29218DB0CF421FBF6DE432@BN0PR11MB5757.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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