From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] disas/capstone: Fix monitor disassembly of >32 bytes
Date: Fri, 30 Oct 2020 14:46:10 +0000 [thread overview]
Message-ID: <CAFEAcA-1rZQT=j48+hn_h4K4D8St_jYmiMU_UKOFvam5pQJ_wA@mail.gmail.com> (raw)
In-Reply-To: <b073898a-4be2-3b06-96d6-7551a9d1a6f3@amsat.org>
On Thu, 22 Oct 2020 at 14:52, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> On 10/22/20 3:24 PM, Peter Maydell wrote:
> > If we're using the capstone disassembler, disassembly of a run of
> > instructions more than 32 bytes long disassembles the wrong data for
> > instructions beyond the 32 byte mark:
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Thanks; applying to target-arm.next since nobody else has
picked it up yet.
-- PMM
prev parent reply other threads:[~2020-10-30 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 13:24 [PATCH] disas/capstone: Fix monitor disassembly of >32 bytes Peter Maydell
2020-10-22 13:52 ` Philippe Mathieu-Daudé
2020-10-30 14:46 ` Peter Maydell [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='CAFEAcA-1rZQT=j48+hn_h4K4D8St_jYmiMU_UKOFvam5pQJ_wA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.org \
/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 NNTP newsgroup(s).