From: Anurekh Saxena <anurekh.saxena@timesys.com>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
kgdb-bugreport@lists.sourceforge.net,
Anurekh Saxena <anurekh.saxena@timesys.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Kgdb-bugreport] kgdb_arch_set/remove_break() ?
Date: Wed, 24 Mar 2004 15:24:02 -0500 [thread overview]
Message-ID: <20040324202402.GA20260@timesys.com> (raw)
In-Reply-To: <200403242005.21197.amitkale@emsyssoft.com>
On Wed, Mar 24, 2004 at 08:05:21PM +0530, Amit S. Kale wrote:
> On Friday 19 Mar 2004 9:33 pm, Tom Rini wrote:
> > Hi. Right now I'm writing up a porting doc that describes the various
> > hook functions we've got. I noticed that nothing is calling
> > kgdb_arch_set/remove_break. Is there some arch we're expecting will
> > need this? I'd like to just go ahead and remove them
>
> I can't remember why that was done. A processor other than PPC, x86 and x86_64
> needs a special implementation of set and remove breakpoint, I guess.
>
> Anurekh, who did initial implementation of arch independent-dependent split
> may have some comments on this.
*set_break
*remove_break
These functions should only be defined for architecutes that support
hardware breakpoint. Set KGDB_HW_BREAKPOINT flag.
next prev parent reply other threads:[~2004-03-24 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 16:03 kgdb_arch_set/remove_break() ? Tom Rini
2004-03-24 14:35 ` [Kgdb-bugreport] " Amit S. Kale
2004-03-24 20:24 ` Anurekh Saxena [this message]
2004-03-24 21:40 ` Tom Rini
[not found] ` <200403251554.39598.amitkale@emsyssoft.com>
2004-03-25 19:37 ` Tom Rini
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=20040324202402.GA20260@timesys.com \
--to=anurekh.saxena@timesys.com \
--cc=amitkale@emsyssoft.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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