From: Shahab Vahedi <shahab.vahedi@gmail.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Simon Marchi <simark@simark.ca>,
Luis Machado <luis.machado@linaro.org>,
Shahab Vahedi <shahab@synopsys.com>
Subject: Re: Why enforcing sw_breakpoint_from_kind() implementation in GDBserver targets
Date: Mon, 15 Jun 2020 12:39:13 +0200 [thread overview]
Message-ID: <20200615103913.GA1816@gmail.com> (raw)
In-Reply-To: <SN6PR11MB2893A094069EB468794DA0B7C4810@SN6PR11MB2893.namprd11.prod.outlook.com>
Tankut,
Thank you for your clear response. I have only one remark:
On Fri, Jun 12, 2020 at 11:04:08AM +0000, Aktemur, Tankut Baris wrote:
> So, the base linux target delegates the op to the low target and enforces
> an implementation.
What about scenarios that "sw_breakpoint_from_kind" for the linux is
defined by the target? There would be no execution of base-linux-target
flavour of "sw_breakpoint_from_kind". Hence, not a mandatory dependency
to the low target's "sw_breakpoint_from_kind".
This scenario is actally not far fetched. That's what's happening in ARC
port.
Shahab
next prev parent reply other threads:[~2020-06-15 10:39 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 [this message]
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
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=20200615103913.GA1816@gmail.com \
--to=shahab.vahedi@gmail.com \
--cc=gdb@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=shahab@synopsys.com \
--cc=simark@simark.ca \
--cc=tankut.baris.aktemur@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).