From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Wrong hw_watchpoint_used_count? (multiple location watchpoints)
Date: Fri, 08 Jan 2010 13:09:00 -0000 [thread overview]
Message-ID: <20100108130858.GF29312@adacore.com> (raw)
In-Reply-To: <83zl4oah5f.fsf@gnu.org>
> That _is_ the design. However, GDB does not tell enough to the target
> for the target to give an accurate answer. And what's more, some
> questions cannot be answered without actually trying to call ptrace or
> its equivalents, and getting its ``opinion''. Unless we mirror all
> the necessary information on the target level that is (which is what
> x86 does).
Hmmm, so you're saying that the situation on x86 is because we cannot
know in advance how many watchpoints the CPU provides?
--
Joel
next prev parent reply other threads:[~2010-01-08 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 7:57 Joel Brobecker
2010-01-08 9:58 ` Eli Zaretskii
2010-01-08 10:30 ` Joel Brobecker
2010-01-08 12:11 ` Eli Zaretskii
2010-01-08 12:26 ` Joel Brobecker
2010-01-08 13:00 ` Eli Zaretskii
2010-01-08 13:09 ` Joel Brobecker [this message]
2010-01-08 16:49 ` 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=20100108130858.GF29312@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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