From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19557 invoked by alias); 22 Aug 2002 22:33:45 -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 19550 invoked from network); 22 Aug 2002 22:33:44 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 22 Aug 2002 22:33:44 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id PAA07949; Thu, 22 Aug 2002 15:27:46 -0700 (PDT) Message-ID: <3D6566C1.DBE3FFD1@redhat.com> Date: Thu, 22 Aug 2002 15:38:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: Andrew Cagney 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> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00732.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?