From: "Emilio G. Cota" <cota@braap.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Richard Henderson <richard.henderson@linaro.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] target/ppc: gdbstub single-step broken since TranslatorOps conversion
Date: Fri, 29 Jun 2018 14:56:41 -0400 [thread overview]
Message-ID: <20180629185641.GC14726@flamenco> (raw)
In-Reply-To: <a0d80637-24e1-12fd-d667-0e06f2a80488@ilande.co.uk>
On Fri, Jun 29, 2018 at 19:38:02 +0100, Mark Cave-Ayland wrote:
> On 29/06/18 19:18, Emilio G. Cota wrote:
> >I tried the last known good commit (as per your bisect) and get the same results
> >as above.
> >
> >Is there any other way I could try reproducing this? Also, can you
> >reproduce with another gdb version?
>
> Hmmm. Have you got a "git clone" of the OpenBIOS source in roms/ that you
> can add to the gdb source path to make sure that "n" correlates with the
> source file line numbers?
I just cloned it and pointed to it using substitute-path in gdb. I
get the same (good) outcome, except that I see the corresponding source.
> >If I don't manage to reproduce, I can send you off-list some patches to try,
> >basically breaking down the diff in the first bad commit into very small chunks,
> >to see where the problem was introduced.
>
> If the above doesn't work, please do, and I will test them and report back.
Will do.
Cheers,
Emilio
prev parent reply other threads:[~2018-06-29 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 12:17 [Qemu-devel] target/ppc: gdbstub single-step broken since TranslatorOps conversion Mark Cave-Ayland
2018-06-29 18:18 ` Emilio G. Cota
2018-06-29 18:38 ` Mark Cave-Ayland
2018-06-29 18:56 ` Emilio G. Cota [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=20180629185641.GC14726@flamenco \
--to=cota@braap.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.