From: Daniel Jacobowitz <drow@false.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: Reporting 'out of hardware breakpoints' situation
Date: Wed, 24 Jun 2009 17:47:00 -0000 [thread overview]
Message-ID: <20090624174653.GA12412@caradoc.them.org> (raw)
In-Reply-To: <4A4263F1.6060209@caviumnetworks.com>
On Wed, Jun 24, 2009 at 10:35:45AM -0700, David Daney wrote:
> It is a difficult problem. There is also the case where multiple
> hardware breakpoints can be covered by a single hardware watch
> register (if two or more watched locations were adjacent in memory).
> It makes it difficult to know exactly how many breakpoints you can
> support.
FYI, I noticed a target we're working on that has two ways to
implement hardware breakpoints. One only works in a certain address
space, and the other shares hardware resources with watchpoints.
So figuring out how many breakpoints are available is pretty
complex.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-24 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:58 Vladimir Prus
2009-06-24 17:37 ` David Daney
2009-06-24 17:47 ` Daniel Jacobowitz [this message]
2009-06-24 17:56 ` Eli Zaretskii
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=20090624174653.GA12412@caradoc.them.org \
--to=drow@false.org \
--cc=ddaney@caviumnetworks.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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