From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-55203-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 23733 invoked by alias); 17 Apr 2008 09:25:28 -0000
Received: (qmail 23714 invoked by uid 22791); 17 Apr 2008 09:25:27 -0000
X-Spam-Check-By: sourceware.org
Received: from ns1.suse.de (HELO mx1.suse.de) (195.135.220.2)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 17 Apr 2008 09:25:02 +0000
Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) 	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) 	(No client certificate requested) 	by mx1.suse.de (Postfix) with ESMTP id 0293C4092D 	for <gdb-patches@sourceware.org>; Thu, 17 Apr 2008 11:25:00 +0200 (CEST)
From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements
References: <20070916183949.GA23966@caradoc.them.org> 	<20071001002015.GA15835@caradoc.them.org> 	<jeej95ctk8.fsf@sykes.suse.de> 	<20080416224910.GA3716@caradoc.them.org> 	<jeabjtcsfb.fsf@sykes.suse.de> 	<20080416231831.GB6274@caradoc.them.org> 	<je63ugu9iw.fsf@sykes.suse.de>
X-Yow: These PRESERVES should be FORCE-FED to PENTAGON OFFICIALS!!
Date: Thu, 17 Apr 2008 09:59:00 -0000
In-Reply-To: <je63ugu9iw.fsf@sykes.suse.de> (Andreas Schwab's message of "Thu, 	17 Apr 2008 11:15:51 +0200")
Message-ID: <jey77csuj8.fsf@sykes.suse.de>
User-Agent: Gnus/5.110008 (No Gnus v0.8) Emacs/22.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-04/txt/msg00327.txt.bz2

Andreas Schwab <schwab@suse.de> writes:

> Daniel Jacobowitz <drow@false.org> writes:
>
>> We need to communicate this to bpstat_stop_status again after the
>> step.  It's supposed to happen automatically, because only a call to
>> watchpoints_triggered ever clears the watchpoint_triggered flag.
>> How is it getting lost?  I assume that it is getting lost; you
>> could set a breakpoint on bpstat_stop_status when it is called
>> just before the "random signal 5", after infwait_nonstep_watch_state,
>> and check.
>
> watchpoint_triggered is not set.  What does that mean?

In fact, it's _never_ set.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."