Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: ARM7, remote GDB, Software Breakpoints
Date: Wed, 12 Feb 2003 20:49:00 -0000	[thread overview]
Message-ID: <20030212204915.GA575@nevyn.them.org> (raw)
In-Reply-To: <200302122117.58218.tmohr@s.netic.de>

On Wed, Feb 12, 2003 at 09:17:58PM +0100, Torsten Mohr wrote:
> Hi,
> 
> thanks for your hint.
> 
> > > 1. I could handle HW breakpoints, how can i tell GDB that it should
> > > use HW breakpoints?  Just answering requests for SW breakpoints with
> > > "ENN" doesn't seem to make GDB use HW breakpoints.
> >
> > You have to implement commands starting with 'Z' and 'z' in order to
> > support hw breakpoints.
> 
> Yes, i do that.  According to GDB remote protocol, when i answer
> a request for "Z0..." with "ENN" (means "i can't handle software
> breakpoints"), GDB doesn't try hardware breakpoints.
> 
> But maybe, when i have some hardware that doesn't run in RAM,
> but in Flash-ROM, i think i'd rather like to have HW breakpoints.
> Also, when i don't answer with "ENN", but with "" (empty),
> GDB doesn't try HW breakpoints.

This was touched recently.  The remote logic decides that 0 hardware
breakpoint resources are available; I don't remember if the patch to
fix it was checked in.  You might want to ask Andrew if he remembers
the problem.

There's probably something in the host gdb you have to set.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-12 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12  6:01 Torsten Mohr
2003-02-12 17:42 ` Quality Quorum
2003-02-12 20:20   ` Torsten Mohr
2003-02-12 20:49     ` Daniel Jacobowitz [this message]
2003-02-13  0:55       ` Steven Johnson
2003-02-13 17:14       ` Andrew Cagney
2003-02-12 21:27     ` Quality Quorum

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=20030212204915.GA575@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.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