From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <archer-return-2257-listarch-archer=sourceware.org@sourceware.org>
Received: (qmail 22815 invoked by alias); 19 Oct 2010 18:19:15 -0000
Mailing-List: contact archer-help@sourceware.org; run by ezmlm
Sender: <archer@sourceware.org>
Precedence: bulk
List-Post: <mailto:archer@sourceware.org>
List-Help: <mailto:archer-help@sourceware.org>
List-Subscribe: <mailto:archer-subscribe@sourceware.org>
List-Id: <archer.sourceware.org>
Received: (qmail 22801 invoked by uid 22791); 19 Oct 2010 18:19:14 -0000
X-SWARE-Spam-Status: No, hits=-6.4 required=5.0
	tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Date: Tue, 19 Oct 2010 18:19:00 -0000
From: Oleg Nesterov <oleg@redhat.com>
To: archer@sourceware.org
Subject: Re: BUG? gdb, software watchpoints && multithreading
Message-ID: <20101019181430.GA10472@redhat.com>
References: <20101012185548.GA19475@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20101012185548.GA19475@redhat.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-SW-Source: 2010-q4/txt/msg00019.txt.bz2

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.