From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] btrace, testsuite: fix spurious gdb.btrace/tsx.exp fails
Date: Fri, 18 Sep 2015 11:44:00 -0000 [thread overview]
Message-ID: <55FBF91C.8070703@redhat.com> (raw)
In-Reply-To: <1442565363-13628-1-git-send-email-markus.t.metzger@intel.com>
On 09/18/2015 09:36 AM, Markus Metzger wrote:
> If the atomic section in x86-tsx.S is aborted,
When can that happen? Is it normal that the test sees this?
> the tsx.exp test will fail
> even if the traced output is actually correct.
>
> Consider abort scenarios in the test.
>
> 2015-09-18 Markus Metzger <markus.t.metzger@intel.com>
>
> testsuite/
> * gdb.btrace/tsx.exp: Consider multiple correct outputs in the record
> instruction-history test.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-09-18 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 8:36 Markus Metzger
2015-09-18 11:44 ` Pedro Alves [this message]
2015-09-18 12:13 ` Metzger, Markus T
2015-09-18 12:56 ` Pedro Alves
2015-09-21 6:31 ` 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=55FBF91C.8070703@redhat.com \
--to=palves@redhat.com \
--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