From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12291 invoked by alias); 13 Dec 2011 16:47:27 -0000 Received: (qmail 12277 invoked by uid 22791); 13 Dec 2011 16:47:23 -0000 X-SWARE-Spam-Status: No, hits=-7.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Dec 2011 16:47:10 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBDGl7tx002582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Dec 2011 11:47:07 -0500 Received: from host2.jankratochvil.net (ovpn-116-16.ams2.redhat.com [10.36.116.16]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id pBDGl0ZE015850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 13 Dec 2011 11:47:03 -0500 Date: Tue, 13 Dec 2011 17:23:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: Fix PR remote/13492 Message-ID: <20111213164659.GA9179@host2.jankratochvil.net> References: <201112051601.59664.pedro@codesourcery.com> <201112122030.25365.pedro@codesourcery.com> <20111212203409.GA28419@host2.jankratochvil.net> <201112131612.30315.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201112131612.30315.pedro@codesourcery.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00412.txt.bz2 On Tue, 13 Dec 2011 17:12:30 +0100, Pedro Alves wrote: > > (I do not agree for example with the lwp->stopped_by_watchpoint part as > > multiple watchpoints may get hit on one stop which isn't handled well but that > > is out of the scope of this discussion.) > > I'm not 100% certain that is possible, but in any case, I think that > even if we handled that, we wouldn't ever get as far as > prepare_to_resume before handling all the multiple watchpoints. True. Thanks, Jan