public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: archer@sourceware.org
Subject: Re: BUG? gdb, software watchpoints && multithreading
Date: Tue, 19 Oct 2010 18:19:00 -0000	[thread overview]
Message-ID: <20101019181430.GA10472@redhat.com> (raw)
In-Reply-To: <20101012185548.GA19475@redhat.com>

On 10/12, Oleg Nesterov wrote:
>
> Not that I really blame gdb, without hardware support it is not
> possible to implement this 100% correctly. But I assume this is
> not what we want?
>
> IOW, I think that ugdb should do the following. If any thread changes
> VAR, then all threads should stop and report T05watch to gdb.

This can't help, see "Q: ugdb && watchpoints" I sent.

> Another question. watch/Z2 is always per-process, there is no
> "thread-local" watches, right?
>
> And the last one. If gdb sends '$Z2' to gdbserver, the running
> threads do not participate in monitoring, until gdb stops the
> thread and resumes it again, correct?
>
> Oleg.

      reply	other threads:[~2010-10-19 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 18:59 Oleg Nesterov
2010-10-19 18:19 ` Oleg Nesterov [this message]

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=20101019181430.GA10472@redhat.com \
    --to=oleg@redhat.com \
    --cc=archer@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).