From: Phil Muldoon <pmuldoon@redhat.com>
To: Frysk Hackers <frysk@sourceware.org>
Subject: Optimizing watchpoints
Date: Fri, 28 Sep 2007 21:21:00 -0000 [thread overview]
Message-ID: <46FD7036.2010500@redhat.com> (raw)
I wasn't going to do this in the first pass at watchpoints, but I might
as well as think on it now.
Given that debug registers are very scarce, and that typically there
might be a scenario where we could better optimize watching similar
addresses and ranges, is there an established protocol for this?
I thought about checking addresses and ranges as a simple "we are
already watching this address in another register and scope". But as
usual things get hairy in C when you add in pointers (that pointer to
pointers in structures and so on).
I suspect the answer here is "No" but can't help to ask, and establish
the conversation ;)
Regards
Phil
next reply other threads:[~2007-09-28 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 21:21 Phil Muldoon [this message]
2007-09-30 19:10 ` Mark Wielaard
2007-10-01 1:25 ` Roland McGrath
2007-10-01 8:41 ` Mark Wielaard
2007-10-01 9:11 ` Phil Muldoon
2007-10-01 9:20 ` Mark Wielaard
2007-10-01 17:40 ` Roland McGrath
2007-10-01 17:54 ` Phil Muldoon
2007-10-10 7:11 ` Phil Muldoon
2007-10-10 10:28 ` Mark Wielaard
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=46FD7036.2010500@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).