Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Wrong hw_watchpoint_used_count? (multiple location watchpoints)
Date: Fri, 08 Jan 2010 16:49:00 -0000	[thread overview]
Message-ID: <83r5q0a6fw.fsf@gnu.org> (raw)
In-Reply-To: <20100108130858.GF29312@adacore.com>

> Date: Fri, 8 Jan 2010 17:08:58 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.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?

On x86 we do know.  On other architectures we might not be able to
know.  But even on x86, breakpoint.c does not pass enough information
to the target for the latter to know if the requested watchpoints will
be successfully inserted.  For that, GDB would need to provide the
address of each watchpoint, its type (read/write), and the length of
the watched area.  It currently does not provide that.


      reply	other threads:[~2010-01-08 16:49 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
2010-01-08 16:49             ` 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=83r5q0a6fw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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