From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements
Date: Sat, 22 Sep 2007 15:37:00 -0000 [thread overview]
Message-ID: <20070922153709.GA10743@caradoc.them.org> (raw)
In-Reply-To: <uvea2zt2z.fsf@gnu.org>
On Sat, Sep 22, 2007 at 04:13:24PM +0200, Eli Zaretskii wrote:
> > > > +@value{GDBN} only supports process-wide watchpoints.
> > >
> > > "Process-wide watchpoints'' as opposed to what?
> >
> > As opposed to thread-specific watchpoints. We can make a watchpoint
> > act like it is thread-specific (or we will be able to once Luis's
> > patch is done), but we don't support setting hardware watchpoints that
> > only trigger in a specific thread. Yet, anyway.
>
> I think you should add something like this explanation, to make the
> intent clear.
Is this clearer?
@value{GDBN} only supports process-wide watchpoints, which trigger in
all threads. If the target supports threads, per-thread debug
registers, and watchpoints which only affect a single thread, it
should set the per-thread debug registers for all threads to the same
value. On @sc{gnu}/Linux native targets, this is accomplished by
using @code{ALL_LWPS} in @code{target_insert_watchpoint} and
@code{target_remove_watchpoint} and by using
@code{linux_set_new_thread} to register a handler for newly created
threads.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-22 15:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:40 Daniel Jacobowitz
2007-09-22 9:03 ` Eli Zaretskii
2007-09-22 14:04 ` Daniel Jacobowitz
2007-09-22 14:13 ` Eli Zaretskii
2007-09-22 15:37 ` Daniel Jacobowitz [this message]
2007-09-22 15:46 ` Eli Zaretskii
2007-09-22 18:28 ` Daniel Jacobowitz
2007-10-01 0:20 ` Daniel Jacobowitz
2007-10-24 14:59 ` Luis Machado
2007-10-24 16:00 ` Daniel Jacobowitz
2007-10-24 16:42 ` Luis Machado
2007-10-24 16:51 ` Daniel Jacobowitz
2007-10-24 18:08 ` Luis Machado
2007-10-24 18:20 ` Daniel Jacobowitz
2008-04-16 22:57 ` Andreas Schwab
2008-04-16 23:05 ` Daniel Jacobowitz
2008-04-16 23:18 ` Andreas Schwab
2008-04-17 0:25 ` Daniel Jacobowitz
2008-04-17 9:52 ` Andreas Schwab
2008-04-17 9:59 ` Andreas Schwab
2008-04-17 10:17 ` Andreas Schwab
2008-04-17 14:53 ` Daniel Jacobowitz
2008-04-20 2:35 ` Andreas Schwab
2008-04-23 11:55 ` Andreas Schwab
2008-04-23 19:46 ` Eli Zaretskii
2008-05-01 19:30 ` Daniel Jacobowitz
2008-05-01 19:50 ` Luis Machado
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=20070922153709.GA10743@caradoc.them.org \
--to=drow@false.org \
--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