From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8553 invoked by alias); 18 Nov 2010 17:22:19 -0000 Received: (qmail 8545 invoked by uid 22791); 18 Nov 2010 17:22:18 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Nov 2010 17:22:13 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 638D82BABF3; Thu, 18 Nov 2010 12:22:11 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hQhYHmb2BlZn; Thu, 18 Nov 2010 12:22:11 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 34C972BABB7; Thu, 18 Nov 2010 12:22:11 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 6D961145B6C; Thu, 18 Nov 2010 09:22:09 -0800 (PST) Date: Thu, 18 Nov 2010 17:22:00 -0000 From: Joel Brobecker To: Pierre Muller Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Improve amd64 prologue analysis Message-ID: <20101118172209.GE2634@adacore.com> References: <001701cb84ea$6883c170$398b4450$@muller@ics-cnrs.unistra.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001701cb84ea$6883c170$398b4450$@muller@ics-cnrs.unistra.fr> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-11/txt/msg00239.txt.bz2 > Free Pascal for x86_64 (amd64) CPU generates losts of functions > that do not use RBP as a frame pointer. > I tried to improve amd64-tdep.c to better cope > with this case. I thought that on amd64, we weren't going to have prologue parsers and rely on frame unwinding info instead? At AdaCore, we have the same sort of things because of Windows where the system code (mostly system DLLs) does not have the unwinding info in DWARF format. But for code generated by us, we have all the debugging information needed to unwind without parsing the prologue, even on Windows64. -- Joel