Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tromey@adacore.com>
Cc: "andrew.burgess@embecosm.com" <andrew.burgess@embecosm.com>,
	Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Avoid self-test failures on x86-linux
Date: Fri, 29 Oct 2021 11:51:19 -0300	[thread overview]
Message-ID: <4e8c0fca-3321-8f63-29d5-3af953973195@linaro.org> (raw)
In-Reply-To: <87h7cznb0d.fsf@tromey.com>

On 10/29/21 11:47 AM, Tom Tromey wrote:
> 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 haven't filed a PR yet. I pinged Andrew about it on IRC to check if 
that was intended behavior or not.
> 
> 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.

It is not immediately obvious that the gdb.base/all-architectures*.exp 
failures are related to disassembler self tests. I wouldn't expect so, 
given those tests invoke "disassemble" explicitly.

      reply	other threads:[~2021-10-29 14:51 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
2021-10-29 14:51       ` Luis Machado via Gdb-patches [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=4e8c0fca-3321-8f63-29d5-3af953973195@linaro.org \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.com \
    --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