From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25851 invoked by alias); 27 Apr 2002 00:36:16 -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 25834 invoked from network); 27 Apr 2002 00:36:15 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 27 Apr 2002 00:36:15 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C99E73CAB; Fri, 26 Apr 2002 20:36:14 -0400 (EDT) Message-ID: <3CC9F27E.1060902@cygnus.com> Date: Fri, 26 Apr 2002 17:36:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020424 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michal Ludvig Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Simple patch for x86-64 (can go to 5.2?) References: <3CC96A2D.5000203@suse.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg01098.txt.bz2 > This patch is a really simple one without any side-effects. The problem is, that gcc for x86-64 by default has -fomit-frame-pointer switched on when optimalization is requested. People don't know it and are complaining that (diplomaticaly said) "gdb doesn't work" (depending on their attitude :-). The only thing this patch does is, that it prints a note, when x86_64_skip_prologue doesn't see "push %rbp" as the very first instruction of a given function. The note is printed only once. That's all. I'd like to see it in 5.2 to teach people that they should explicitly use -fno-omit-frame-pointer when compiling a code for debugging. Can I commit? I'll remove this note as soon as I fix dwarf2 reader to handle even optimized code. > > 2002-04-26 Michal Ludvig > * x86-64-tdep.c (x86_64_skip_prologue): Print note when debugging > code without frame pointers. Sigh (you've figured out the one thing that will make me delay a release :-) Yes, I've committed it (can you please create a bug report explaining the warning message). Andrew