From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6060 invoked by alias); 10 Jan 2008 15:46:21 -0000 Received: (qmail 6052 invoked by uid 22791); 10 Jan 2008 15:46:21 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Jan 2008 15:45:58 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 063199811D; Thu, 10 Jan 2008 15:45:57 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id CB9E8980E0; Thu, 10 Jan 2008 15:45:56 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JCzbP-0005mn-Od; Thu, 10 Jan 2008 10:45:55 -0500 Date: Thu, 10 Jan 2008 15:46:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Joel Brobecker , gdb-patches@sourceware.org Subject: Re: [RFC/RFA?] Should break FILE:LINENO skip prologue? Message-ID: <20080110154555.GA22176@caradoc.them.org> Mail-Followup-To: Michael Snyder , Joel Brobecker , gdb-patches@sourceware.org References: <20080109151745.GA13181@adacore.com> <1199910284.14654.13.camel@localhost.localdomain> <20080109203453.GI21281@adacore.com> <1199912695.14654.21.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1199912695.14654.21.camel@localhost.localdomain> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00239.txt.bz2 On Wed, Jan 09, 2008 at 01:04:55PM -0800, Michael Snyder wrote: > Don't forget my argument about prologue initializations. > Sometimes those involve function calls. A user might very > well want to stop AFTER some of those function calls, but > BEFORE others, so he could step into them. > > Especially in C++, where some of them would be constructors. This argument doesn't apply; local variable initializations are not part of the function prologue. GCC will attribute them to the lines on which they were written. Only setting up the stack frame and saving incoming arguments to the stack are part of the prologue. -- Daniel Jacobowitz CodeSourcery