From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: ddaney@caviumnetworks.com, vladimir@codesourcery.com,
gdb@sources.redhat.com
Subject: Re: Reporting 'out of hardware breakpoints' situation
Date: Wed, 24 Jun 2009 17:56:00 -0000 [thread overview]
Message-ID: <83fxdpbjoa.fsf@gnu.org> (raw)
In-Reply-To: <20090624174653.GA12412@caradoc.them.org>
> Date: Wed, 24 Jun 2009 13:46:54 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
>
> So figuring out how many breakpoints are available is pretty
> complex.
I think it's pretty much impossible. (We have a similar problem with
hardware watchpoints.) Several breakpoints can be set to the same
address, in which case a single register can serve all of them, but
deciding that this is the case is tricky at best.
I think the way of throwing an exception and then handling it to
revert to the original state is much more promising.
prev parent reply other threads:[~2009-06-24 17:56 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
2009-06-24 17:56 ` Eli Zaretskii [this message]
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=83fxdpbjoa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ddaney@caviumnetworks.com \
--cc=drow@false.org \
--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