From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Don't delete local watchpoints just because a different thread stopped.
Date: Fri, 20 Nov 2009 01:14:00 -0000 [thread overview]
Message-ID: <20091120011305.GA9797@caradoc.them.org> (raw)
In-Reply-To: <200911200030.50194.pedro@codesourcery.com>
On Fri, Nov 20, 2009 at 12:30:50AM +0000, Pedro Alves wrote:
> On Thursday 19 November 2009 17:45:39, Daniel Jacobowitz wrote:
> > For all-stop, do we want to check whenever the watchpoint's thread is
> > stopped?
>
> Yep (non-stop), good catch. Usually we'd get here with a stopped
> thread, but there's always say,
No, I really meant all-stop.
Suppose one thread hits a breakpoint, and another thread hits a
watchpoint while we're trying to stop it. Is there any reason not to
temporarily switch threads to check? Or any reason to, for that
matter - I'm not sure.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-11-20 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 2:07 Pedro Alves
2009-11-19 17:46 ` Daniel Jacobowitz
2009-11-20 0:31 ` Pedro Alves
2009-11-20 1:14 ` Daniel Jacobowitz [this message]
2009-11-20 1:33 ` Pedro Alves
2009-11-20 3:47 ` 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=20091120011305.GA9797@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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