From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27926 invoked by alias); 12 Jun 2005 14:28:44 -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 27907 invoked by uid 22791); 12 Jun 2005 14:28:40 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 12 Jun 2005 14:28:40 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DhTRy-0006Yb-ME; Sun, 12 Jun 2005 10:28:34 -0400 Date: Sun, 12 Jun 2005 14:28:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Klee Dienes , gdb-patches@sources.redhat.com Subject: Re: The gdb x86 function prologue parser Message-ID: <20050612142834.GA24699@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Klee Dienes , gdb-patches@sources.redhat.com References: <85C775AE-3B05-431E-96D2-49EA9D1413E6@apple.com> <20050608132431.GA4970@nevyn.them.org> <20050608095805.A67988@molenda.com> <200506120748.j5C7m75C011986@elgar.sibelius.xs4all.nl> <3364FC4D-63FB-493B-9136-D118F74C13BB@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00133.txt.bz2 Hmm, Klee's message didn't make it to the list. On Sun, Jun 12, 2005 at 04:17:38PM +0300, Eli Zaretskii wrote: > > Cc: Mark Kettenis , jason-swarelist@molenda.com, > > gdb-patches@sources.redhat.com > > From: Klee Dienes > > Date: Sun, 12 Jun 2005 07:59:01 -0400 > > > > (2) gets used by GDB when it wants to know where to set a breakpoint > > (the idea being that when you say "break foo", it wants to insert the > > breakpoint in foo() after the prologue has been fully executed). > > > > It also gets used where GDB wants to know if it is inside a function > > prologue for some reason (for example, so "next" knows if it has > > stepped into a new function, or simply jumped interprocedurally). > > Thanks. > > (I'm collecting info for gdbint.texinfo, that's why I asked.) FYI, the second part is decreasingly true now. I only see one reference to in_prologue left in infrun, and I'm pretty sure it's obsolete. Most uses are for the first reason. And the first reason should, IMO, go away. But it's a lot of work to support stopping at the very beginning of a function, and still printing arguments correctly, without help from the compiler. We don't have a clear plan on how to do that yet. -- Daniel Jacobowitz CodeSourcery, LLC