From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21344 invoked by alias); 24 Jul 2007 19:08:32 -0000 Received: (qmail 21336 invoked by uid 22791); 24 Jul 2007 19:08:32 -0000 X-Spam-Check-By: sourceware.org Received: from chip8og57.obsmtp.com (HELO chip8og57.obsmtp.com) (64.18.15.187) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 24 Jul 2007 19:08:27 +0000 Received: from source ([12.110.134.31]) by chip8ob57.postini.com ([64.18.7.12]) with SMTP; Tue, 24 Jul 2007 12:07:15 PDT Received: from pkoning-laptop.equallogic.com.equallogic.com ([172.25.202.120]) by M31.equallogic.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Jul 2007 15:07:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18086.19957.724795.671305@pkoning-laptop.equallogic.com> Date: Wed, 25 Jul 2007 02:18:00 -0000 From: Paul Koning To: eager@eagercon.com Cc: mark.kettenis@xs4all.nl, gdb@sources.redhat.com, vladimir@codesourcery.com Subject: Re: frame cache References: <46A63051.7060208@eagercon.com> <20070724171452.GA15843@caradoc.them.org> <46A6387F.8020303@eagercon.com> <200707241832.l6OIWAUp018805@brahms.sibelius.xs4all.nl> <46A648BC.8070105@eagercon.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00182.txt.bz2 >>>>> "Michael" == Michael Eager writes: Michael> Mark Kettenis wrote: >> If that's the case, there's something wrong; prologue analysis >> should only be done as a last resort, i.e. when proper debug >> information is not available. >> >> Your effort might be better spent on determining why proper debug >> info is not present instead of optimizing >> _analyze_prologue(). Michael> Perhaps so, I don't see where other targets check for debug Michael> info before calling analyze_prologue(). For example, on Michael> i386, i386_analyze_prologue() is called each and every time Michael> that i386_skip_prologue() is called. I've run into other cases, with assembly language code in kernels. It may be that this could be cured by throwing in more magic assembly language pseudo-ops. Then again, I have a modified GDB that usees prologue analysis to handle not just function calls, but also interrupts and exceptions; this is quite handy in RTOS work. paul