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 09:58:00 -0000	[thread overview]
Message-ID: <83fx6gc43p.fsf@gnu.org> (raw)
In-Reply-To: <20100108075701.GE4589@adacore.com>

> Date: Fri, 8 Jan 2010 11:57:01 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> This is mostly from code inspection, while investigating something else,
> but I think that the current implementation of hw_watchpoint_used_count
> is inaccurate. It counts the number of breakpoints which match the given
> type.  But in fact, when I looked at the way the watchpoint is created,
> watchpoints may have multiple bp_locations. So, a better approximation
> would be to count the number of bp_locations, no?
> 
> Even so, this does not appear to be entirely accurate either. For
> instance, if the user tries to watch an entity that does not fit
> in one watchpoint, I think we can still end up with a situation
> where we have one bp_location needing 2 h/w watchpoints.
> In the end, it looks like the only way to really clean things up
> would be to store for each watchpoint the associated number of
> needed hardware watchpoints...

But this is something only the target knows.  There's no way for
breakpoint.c to know that, unless we introduce an API through which
breakpoint.c can ask the target to provide that number.

Please note, for example, that some watchpoints can actually need
*zero* bp_locations, because some other watchpoint already watches the
same address.  x86 uses reference counting to not waste hardware
resources for the same address.


  reply	other threads:[~2010-01-08  9:58 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 [this message]
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

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=83fx6gc43p.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