From: Peter Maydell <peter.maydell@linaro.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
Marcus Shawcroft <marcus.shawcroft@gmail.com>,
Terry.Guo@arm.com, Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
"lgustavo@codesourcery.com" <lgustavo@codesourcery.com>,
yao@codesourcery.com, gdb-patches@sourceware.org,
Will Deacon <Will.Deacon@arm.com>,
"Gareth, McMullin" <gareth@blacksphere.co.nz>
Subject: Re: [RFA/commit] arm-tdep.c: Do not single-step after hitting a watchpoint
Date: Tue, 30 Sep 2014 14:50:00 -0000 [thread overview]
Message-ID: <CAFEAcA8DFVfeQcPQoq5zqm1mqzaSLawmB=BZXoVmBkGf4Ntifw@mail.gmail.com> (raw)
In-Reply-To: <20140930142612.GE6927@adacore.com>
On 30 September 2014 15:26, Joel Brobecker <brobecker@adacore.com> wrote:
> That's very interesting. When I talked to one of our QEMU developers
> in house about this, he wasn't even sure if it was possible for
> QEMU to stop at the instruction triggering the watchpoint. Now,
> we know it is, but it could be simpler for QEMU to implement the
> same policy on all targets.
QEMU's stub has to implement "act like the hardware does" for
each individual target CPU, because that's what existing gdb
implementations in the field expect. "Act the same in the
stub regardless of target CPU" is what we used to do and
the result was not stopping in the right place.
The actual in-QEMU implementation is pretty trivial, since
we already need to support both behaviours in order to
correctly emulate the architectural debug support we
expose to guest OSes, and it's then just a matter of
setting or not setting a flag when we set up the wp.
-- PMM
next prev parent reply other threads:[~2014-09-30 14:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 18:23 Peter Maydell
2014-09-29 22:15 ` Pedro Alves
2014-09-29 22:54 ` Peter Maydell
2014-09-30 9:08 ` Pedro Alves
2014-09-30 9:18 ` Will Deacon
2014-09-30 10:07 ` Pedro Alves
2014-09-30 10:18 ` Peter Maydell
2014-09-30 10:38 ` Pedro Alves
2014-09-30 10:01 ` Peter Maydell
2014-09-30 10:34 ` Pedro Alves
2014-09-30 12:54 ` Pedro Alves
2014-09-30 13:50 ` Joel Brobecker
2014-09-30 14:11 ` Pedro Alves
2014-09-30 14:26 ` Joel Brobecker
2014-09-30 14:50 ` Peter Maydell [this message]
2014-09-30 8:57 ` Will Deacon
2014-09-30 9:04 ` Will Deacon
2014-09-30 9:14 ` Pedro Alves
2014-09-30 9:24 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2014-09-15 13:01 Joel Brobecker
2014-09-16 11:12 ` Yao Qi
2014-09-16 11:59 ` Joel Brobecker
2014-09-16 12:05 ` Luis Machado
2014-09-16 12:48 ` Joel Brobecker
2014-09-16 13:09 ` Luis Machado
2014-09-16 15:21 ` Pedro Alves
2014-09-18 11:40 ` Marcus Shawcroft
2014-09-19 17:31 ` Pedro Alves
2014-09-29 17:51 ` Joel Brobecker
2014-09-29 17:57 ` Luis Machado
2014-09-29 21:04 ` Pedro Alves
2014-09-30 8:54 ` Will Deacon
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='CAFEAcA8DFVfeQcPQoq5zqm1mqzaSLawmB=BZXoVmBkGf4Ntifw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=Marcus.Shawcroft@arm.com \
--cc=Terry.Guo@arm.com \
--cc=Will.Deacon@arm.com \
--cc=brobecker@adacore.com \
--cc=gareth@blacksphere.co.nz \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=marcus.shawcroft@gmail.com \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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