Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch] Watchpoints: support for thread <thread_num> parameters
Date: Mon, 20 Aug 2007 14:21:00 -0000	[thread overview]
Message-ID: <20070820142141.GA18034@caradoc.them.org> (raw)
In-Reply-To: <1187618630.4974.5.camel@localhost>

On Mon, Aug 20, 2007 at 11:03:49AM -0300, Luis Machado wrote:
> On Fri, 2007-08-17 at 14:49 -0400, Daniel Jacobowitz wrote:
> > On Fri, Aug 17, 2007 at 09:41:38PM +0300, Eli Zaretskii wrote:
> > > Is this all that needs to be done to have thread-specific watchpoints?
> > > Do they work after this patch as you want them to?
> > 
> > In my opinion, not really.  On some systems, you can tell the target
> > layer which threads the watchpoint should be inserted for and spare
> > yourself extra stops in "wrong" threads.
> 
> What do you have in mind regarding the whole feature? Will we head
> towards a different solution?

The work you've done will still be necessary.  I have no plans to work
on the bigger picture, myself, but thread specificity needs to be
communicated to lower layers somehow.

Consider: in the current status quo the watchpoint would be inserted
in every thread, using up precious hardware debug resources and
triggering unnecessarily.  We'll just resume in threads other than the
indicated one, so we shouldn't set up the watchpoint anywhere else.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-08-20 14:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 21:03 Luis Machado
2007-08-17 10:24 ` Eli Zaretskii
2007-08-17 15:47   ` Luis Machado
2007-08-17 18:41     ` Eli Zaretskii
2007-08-17 18:50       ` Daniel Jacobowitz
2007-08-20 14:28         ` Luis Machado
2007-08-20 14:21           ` Daniel Jacobowitz [this message]
2007-08-20 15:23             ` Luis Machado
2007-08-20 15:29               ` Daniel Jacobowitz
2007-08-23 21:08                 ` Joel Brobecker
2007-08-23 21:15                   ` Luis Machado
2007-10-11 19:40     ` Daniel Jacobowitz
2007-10-11 20:33       ` Luis Machado
2007-11-13 14:50         ` Luis Machado
2007-11-13 15:38           ` Andreas Schwab
2007-11-13 22:30           ` Eli Zaretskii
2007-11-14 12:20             ` Luis Machado
2007-11-30 16:10               ` Luis Machado
2007-12-16 21:50               ` Daniel Jacobowitz
2007-12-17 13:29                 ` Luis Machado
2007-12-19 13:05                   ` [RFC/RFA] testsuite/gdb.base/watch_thread_num.exp: Fix test for systems having hidden threads Pierre Muller
2007-12-19 13:56                     ` Luis Machado
2007-12-19 14:04                       ` Pierre Muller
2007-12-19 14:05                     ` 'Daniel Jacobowitz'
2007-12-19 14:55                       ` Pierre Muller
2007-12-19 15:04                         ` 'Daniel Jacobowitz'

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=20070820142141.GA18034@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    /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