From: "Maciej W. Rozycki" <macro@wdc.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Simon Marchi <simark@simark.ca>,
Shahab Vahedi <shahab.vahedi@gmail.com>,
Luis Machado <luis.machado@linaro.org>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Shahab Vahedi <shahab@synopsys.com>
Subject: RE: Why enforcing sw_breakpoint_from_kind() implementation in GDBserver targets
Date: Wed, 17 Jun 2020 01:40:28 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2006170135340.9519@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <DM5PR11MB1690C83D9D3314AC5A7D952BDE9C0@DM5PR11MB1690.namprd11.prod.outlook.com>
On Mon, 15 Jun 2020, Metzger, Markus T via Gdb wrote:
> > Note that this would only concern GDBserver, other server implementations
> > of the remote protocol are free to support Z0 or not. But we could decide
> > that all GDBserver ports have to support it.
>
> The Intel Graphics architecture uses breakpoint bits inside instructions. There
> is no single breakpoint opcode as there is INT3 on IA, for example.
>
> The breakpoint can be ignored one time, which allows stepping over breakpoints
> without having to remove them. This obviously only works if the breakpoint bit
> in the original instruction is set and the instruction is not replaced with a fixed
> breakpoint pattern.
Hmm, it seems to me like a use case for the breakpoint kind.
Maciej
next prev parent reply other threads:[~2020-06-17 0:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 17:47 Shahab Vahedi
2020-06-11 3:05 ` Simon Marchi
2020-06-11 9:40 ` Shahab Vahedi
2020-06-11 10:35 ` Luis Machado
2020-06-11 11:00 ` Shahab Vahedi
2020-06-11 11:44 ` Shahab Vahedi
2020-06-12 11:04 ` Aktemur, Tankut Baris
2020-06-15 10:39 ` Shahab Vahedi
2020-06-16 13:15 ` Aktemur, Tankut Baris
2020-06-17 21:31 ` Shahab Vahedi
2020-06-17 22:20 ` Luis Machado
2020-06-11 14:51 ` Simon Marchi
2020-06-15 8:54 ` Metzger, Markus T
2020-06-17 0:40 ` Maciej W. Rozycki [this message]
2020-06-18 8:11 ` Metzger, Markus T
2020-06-18 9:13 ` Maciej W. Rozycki
2020-06-18 10:29 ` Metzger, Markus T
2020-06-18 11:03 ` Maciej W. Rozycki
2020-06-18 11:11 ` Metzger, Markus T
2020-06-11 21:21 ` Martin Simmons
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=alpine.LFD.2.21.2006170135340.9519@redsun52.ssa.fujisawa.hgst.com \
--to=macro@wdc.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=markus.t.metzger@intel.com \
--cc=shahab.vahedi@gmail.com \
--cc=shahab@synopsys.com \
--cc=simark@simark.ca \
/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