From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11995 invoked by alias); 12 Jun 2005 08:44:32 -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 11988 invoked by uid 22791); 12 Jun 2005 08:44:29 -0000 Received: from legolas.inter.net.il (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 12 Jun 2005 08:44:29 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-207-5.inter.net.il [83.130.207.5]) by legolas.inter.net.il (MOS 3.5.8-GR) with ESMTP id EOZ59429 (AUTH halo1); Sun, 12 Jun 2005 11:44:20 +0300 (IDT) Date: Sun, 12 Jun 2005 08:44:00 -0000 Message-Id: From: Eli Zaretskii To: Mark Kettenis CC: jason-swarelist@molenda.com, gdb-patches@sources.redhat.com In-reply-to: <200506120748.j5C7m75C011986@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 12 Jun 2005 09:48:07 +0200 (CEST)) Subject: Re: The gdb x86 function prologue parser Reply-to: Eli Zaretskii References: <85C775AE-3B05-431E-96D2-49EA9D1413E6@apple.com> <20050608132431.GA4970@nevyn.them.org> <20050608095805.A67988@molenda.com> <200506120748.j5C7m75C011986@elgar.sibelius.xs4all.nl> X-SW-Source: 2005-06/txt/msg00121.txt.bz2 > Date: Sun, 12 Jun 2005 09:48:07 +0200 (CEST) > From: Mark Kettenis > CC: gdb-patches@sources.redhat.com > > 1. Finding out the gory details about the stack frame being executed. > > 2. Determining the first bit of code after the prologue, i.e. the > first bit of real code. > > For (2) following jumps is usually a very bad thing to do. > > That said, I'm not sure this dual usage of the prologue scanner really > makes sense these days. There is a certain lack of consistency in gdb > how we handle this anyway. Maybe the best thing to do is to not use > the prologue scanner for 2 at all. In what situations would GDB need to use (2), and what are the alternative(s)?