From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30151 invoked by alias); 1 Dec 2005 05:21:47 -0000 Received: (qmail 30143 invoked by uid 22791); 1 Dec 2005 05:21:46 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.199) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 Dec 2005 05:21:46 +0000 Received: by zproxy.gmail.com with SMTP id l1so186938nzf for ; Wed, 30 Nov 2005 21:21:44 -0800 (PST) Received: by 10.36.3.15 with SMTP id 15mr1229139nzc; Wed, 30 Nov 2005 21:21:43 -0800 (PST) Received: by 10.37.2.6 with HTTP; Wed, 30 Nov 2005 21:21:43 -0800 (PST) Message-ID: <8f2776cb0511302121k4b750269l4316b1e13a41debc@mail.gmail.com> Date: Thu, 01 Dec 2005 05:21:00 -0000 From: Jim Blandy To: pgilliam@us.ibm.com Subject: Re: [PATCH] add 'rs6000_in_function_epilogue_p()' Cc: gdb-patches@sources.redhat.com In-Reply-To: <200511301225.56802.pgilliam@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200511301225.56802.pgilliam@us.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00000.txt.bz2 I'm not objecting to the patch, but following the links to the other messages I didn't really see an explanation as to how incorrectly recognizing the prologue causes the watchpoints to be deleted early.=20 I assume we're talking about a case like: - we're in some function foo - we set a watchpoint on one of its local variables - we step through a call from foo to bar - as we exit bar, the watchpoint gets deleted, even though it's in the frame we're returning to, not the frame that is exiting. Is that right? How does correctly recognizing the prologue fix this?