From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4556 invoked by alias); 24 Jul 2007 18:45:23 -0000 Received: (qmail 4545 invoked by uid 22791); 24 Jul 2007 18:45:23 -0000 X-Spam-Check-By: sourceware.org Received: from shell4.BAYAREA.NET (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 24 Jul 2007 18:45:21 +0000 Received: (qmail 17356 invoked from network); 24 Jul 2007 11:45:19 -0700 Received: from 209-128-106-254.bayarea.net (HELO ?192.168.20.7?) (209.128.106.254) by shell4.bayarea.net with SMTP; 24 Jul 2007 11:45:19 -0700 Message-ID: <46A648BC.8070105@eagercon.com> Date: Tue, 24 Jul 2007 19:08:00 -0000 From: Michael Eager User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: Mark Kettenis CC: 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> In-Reply-To: <200707241832.l6OIWAUp018805@brahms.sibelius.xs4all.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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/msg00181.txt.bz2 Mark Kettenis wrote: >> Date: Tue, 24 Jul 2007 10:35:59 -0700 >> From: Michael Eager >> >> When I put debugging code in _analyze_prologue(), I see >> that it is called over and over while executing a "next" command. >> All those bits going back and forth over the serial line to the >> target. > > 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(). Perhaps so, I don't see where other targets check for debug info before calling analyze_prologue(). For example, on i386, i386_analyze_prologue() is called each and every time that i386_skip_prologue() is called. I don't see where there is any test in symtab.c or infrun.c which tests for debug info before calling SKIP_PROLOGUE which calls _skip_prologue. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077