From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30264 invoked by alias); 22 Aug 2002 22:54:54 -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 30256 invoked from network); 22 Aug 2002 22:54:53 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 22 Aug 2002 22:54:53 -0000 Received: from ges.redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 309023C48; Thu, 22 Aug 2002 18:54:51 -0400 (EDT) Message-ID: <3D656BBA.4090803@ges.redhat.com> Date: Thu, 22 Aug 2002 15:56:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020810 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Snyder Cc: Jim Ingham , gdb-patches@sources.redhat.com Subject: Re: [RFC] breakpoints and function prologues... References: <157B023C-B09E-11D6-BDB5-00039379E320@apple.com> <3D5C4FCB.4070005@ges.redhat.com> <3D6566C1.DBE3FFD1@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00734.txt.bz2 > Andrew Cagney wrote: > >> > >> > >> > Most users I have talked to think that setting a break on the "{" at the beginning of a function means the same thing as setting a breakpoint on the function. But that is not the case. "break funcName" is AFTER the prologue, "break file: is the true function beginning. > >> >> Don't forget that ``break func'' is is going to change. It's going to >> go back to the start of the function! > > > ??? > Since when? When an architecture enables CFI. CFI removes any technical reason for skipping the prologue (what break foo does'') -- CFI allows you to find the value of registers and variables at any point in the code. Of course,we could always leave ``break foo''. Andrew