From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>
Cc: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>,
Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH v2] Avoid self-test failures on x86-linux
Date: Fri, 29 Oct 2021 08:47:30 -0600 [thread overview]
Message-ID: <87h7cznb0d.fsf@tromey.com> (raw)
In-Reply-To: <325373ef-31b2-6403-329b-cf8e3fa45c26@linaro.org> (Luis Machado's message of "Fri, 29 Oct 2021 11:28:50 -0300")
Luis> Isn't this a broader issue? I recently reported some failures in the
Luis> gdb.base/all-architectures-2.exp, where disassembling fails due to
Luis> (apparently) some recent changes in error reporting.
Do you have a link?
I've only run into this particular problem, and when I wrote the fix, I
looked through opcodes to find other similar instances, and didn't find
any.
Tom
next prev parent reply other threads:[~2021-10-29 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 19:43 Tom Tromey via Gdb-patches
2021-10-29 13:31 ` Tom Tromey via Gdb-patches
2021-10-29 14:28 ` Luis Machado via Gdb-patches
2021-10-29 14:47 ` Tom Tromey via Gdb-patches [this message]
2021-10-29 14:51 ` Luis Machado via Gdb-patches
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=87h7cznb0d.fsf@tromey.com \
--to=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=tromey@adacore.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