From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12621 invoked by alias); 5 Apr 2002 07:38:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12588 invoked from network); 5 Apr 2002 07:38:55 -0000 Received: from unknown (HELO heimdall.inter.net.il) (192.114.186.17) by sources.redhat.com with SMTP; 5 Apr 2002 07:38:55 -0000 Received: from zaretsky (diup-217-188.inter.net.il [213.8.217.188]) by heimdall.inter.net.il (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id BHH39975; Fri, 5 Apr 2002 10:38:46 +0300 (IDT) Date: Thu, 04 Apr 2002 23:38:00 -0000 From: "Eli Zaretskii" To: drow@mvista.com Message-Id: <6480-Fri05Apr2002103430+0300-eliz@is.elta.co.il> CC: gdb-patches@sources.redhat.com In-reply-to: <20020402184333.A8464@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 2 Apr 2002 18:43:33 -0500) Subject: Re: [RFA] Fix watchpoints when stepping over a breakpoint Reply-to: Eli Zaretskii References: <20020402184333.A8464@nevyn.them.org> X-SW-Source: 2002-04/txt/msg00153.txt.bz2 > Date: Tue, 2 Apr 2002 18:43:33 -0500 > From: Daniel Jacobowitz > > When I tried it I got stuck > on the bp_shlib_event breakpoint. We would hit it, remove, single-step > (trap expected), check where we were... and find ourselves at the > shared library breakpoint again because of DECR_PC_AFTER_BREAK! > > Instead, I now collect only non-breakpoint events. Isn't this a bit ad hoc? I think the issue of doing TRT when both a breakpoint and a watchpoint fire for the same instruction needs a more general solution. While ignoring breakpoints might be the Right Thing in this particular case, I wonder what will be TRT in other cases? Did you try to arrange for a normal breakpoint and a watchpoint on the same instruction, and see what happens in that case, with and without this patch?