Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: "M. David Gelbman" <dgelbman@npiny.com>
Cc: gdb@cygnus.com
Subject: Re: Implimenting MIPS R4650 DWATCH register as hbreak hardware breakpoint
Date: Tue, 13 Apr 1999 20:42:00 -0000	[thread overview]
Message-ID: <37140E7B.955EBE89@cygnus.com> (raw)
In-Reply-To: <3707AE48.2582E501.cygnus.gdb@npiny.com>

"M. David Gelbman" wrote:
> 
> Anybody,
> 
> I'm developing an application on a an IDT MIPS R4650 based board.  this
> MIPS CPU has a DWATCH register capable of breaking on a data read or
> write (or both).
> 
> What must I do to the host portion of GDB to let it know my target is
> capable of implimenting a "hardware" breakpoint?  Further what must I do
> to modify my target GDB stub?
> 
> I suspect the host part is simply a re-configuration of somthing in the
> .gdbini file.  I expect that the target stub needs to parse a new
> command in handle_exception() through the "target remote" protocol.  But
> I haven't yet found the magic words.

FYI,

J.T. Conklin <jtc@redbacknetworks.com> recently posted a proposal (and
patch) to gdb/remote.c that adds hardware breakpoint suport.

At present the proposed protocol changes are accepted but the patch
needed some minor revisions.

Could I suggest finding the thread ``Patch to add breakpoint extension
to remote protocol'' on the gdb-patches mailing list. (Am I foolisly
assuming that gdb-patches is archived?)

	Andrew


       reply	other threads:[~1999-04-13 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3707AE48.2582E501.cygnus.gdb@npiny.com>
1999-04-13 20:42 ` Andrew Cagney [this message]
1999-04-13 21:36   ` Jason Molenda
1999-04-04 11:25 M. David Gelbman
1999-04-04 13:03 ` M. David Gelbman

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=37140E7B.955EBE89@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=dgelbman@npiny.com \
    --cc=gdb@cygnus.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