From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 584 invoked by alias); 10 Jan 2008 21:49:09 -0000 Received: (qmail 545 invoked by uid 22791); 10 Jan 2008 21:49:06 -0000 X-Spam-Check-By: sourceware.org Received: from bluesmobile.specifix.com (HELO bluesmobile.specifix.com) (216.129.118.140) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Jan 2008 21:48:49 +0000 Received: from [127.0.0.1] (bluesmobile.specifix.com [216.129.118.140]) by bluesmobile.specifix.com (Postfix) with ESMTP id 1E1453C0AB; Thu, 10 Jan 2008 13:48:47 -0800 (PST) Subject: Re: [RFC/RFA?] Should break FILE:LINENO skip prologue? From: Michael Snyder To: Daniel Jacobowitz Cc: Joel Brobecker , gdb-patches@sourceware.org In-Reply-To: <20080110154555.GA22176@caradoc.them.org> References: <20080109151745.GA13181@adacore.com> <1199910284.14654.13.camel@localhost.localdomain> <20080109203453.GI21281@adacore.com> <1199912695.14654.21.camel@localhost.localdomain> <20080110154555.GA22176@caradoc.them.org> Content-Type: text/plain Date: Thu, 10 Jan 2008 21:49:00 -0000 Message-Id: <1200001726.14654.31.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-4.fc7) Content-Transfer-Encoding: 7bit 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/msg00248.txt.bz2 On Thu, 2008-01-10 at 10:45 -0500, Daniel Jacobowitz wrote: > 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. In that event, my concerns are much alleviated. ;-)