From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
robertsong.japan@gmail.com, gdb@sourceware.org
Subject: Re: Why no hwatch command in gdb ?
Date: Thu, 10 Mar 2011 11:34:00 -0000 [thread overview]
Message-ID: <20110310113421.GV19402@adacore.com> (raw)
In-Reply-To: <E1Pxe0v-000453-AA@fencepost.gnu.org>
> If you expect GDB to know up front that they are too many, this is
> hard to impossible with today's architecture, because only when the
> watchpoints are inserted by the target, it is possible to know whether
> there are enough resources for that.
>
> (At least that's how things were back when I hacked x86 watchpoints.)
I've always been confused by the way watchpoints are supported in
GDB, depending on the target platform, etc. I think there was
a recent change that made us insert the watchpoint immediately,
as a way to check whether we have resources or not. I don't
know how much this helps in practice.
--
Joel
next prev parent reply other threads:[~2011-03-10 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 7:25 robert song
2011-03-10 8:12 ` Jan Kratochvil
2011-03-10 10:09 ` robert song
2011-03-10 10:34 ` Jan Kratochvil
2011-03-10 11:26 ` Eli Zaretskii
2011-03-10 11:34 ` Joel Brobecker [this message]
2011-03-10 12:27 ` Pedro Alves
2011-03-10 11:55 ` Jan Kratochvil
2011-03-10 14:47 ` Frank Ch. Eigler
2011-03-10 12:18 ` robert song
2011-03-10 13:45 ` Jan Kratochvil
2011-03-10 14:47 ` Philippe Waroquiers
2011-03-10 21:04 ` Tom Tromey
2011-03-11 7:58 ` Philippe Waroquiers
2011-03-11 17:48 ` Daniel Jacobowitz
2011-03-10 8:23 paawan oza
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=20110310113421.GV19402@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=robertsong.japan@gmail.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