From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15322 invoked by alias); 31 Jul 2002 20:47:38 -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 15313 invoked from network); 31 Jul 2002 20:47:36 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 31 Jul 2002 20:47:36 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id 3E8A65EA11; Wed, 31 Jul 2002 15:47:35 -0500 (EST) To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] breakpoints and function prologues... References: <20020722231957.GE4999@gnat.com> <20020726053320.GB10000@gnat.com> <20020731013453.GX13411@gnat.com> From: Jim Blandy Date: Wed, 31 Jul 2002 13:55:00 -0000 In-Reply-To: <20020731013453.GX13411@gnat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg00632.txt.bz2 For as long as I can remember, GDB has treated setting a breakpoint on the line containing the opening curly brace of a function's block as meaning `set a breakpoint before the prologue'. I've always assumed that was deliberate behavior. But I can't find it documented in the GDB manual. And it's a lousy user interface (`break *main' works just as well, and makes more sense to me). Maybe the behavior is just a side effect of the decision to attribute the prologue code to the line containing the opening curly brace --- if the program stops in the prologue, that's as sensible a place as any to claim it's at. So I'd support changing `break LINENO' to always skip the prologue.