From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-25033-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 18461 invoked by alias); 26 Apr 2006 14:59:44 -0000
Received: (qmail 18453 invoked by uid 22791); 26 Apr 2006 14:59:43 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 26 Apr 2006 14:59:41 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54) 	id 1FYlUQ-0005cR-KG; Wed, 26 Apr 2006 10:59:38 -0400
Date: Wed, 26 Apr 2006 18:17:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI: performance of getting stack arguments
Message-ID: <20060426145938.GA21560@nevyn.them.org>
Mail-Followup-To: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
References: <e2331r$cbr$1@sea.gmane.org> <20060418161654.GA15524@nevyn.them.org> <200604191020.08044.ghost@cs.msu.su> <20060419124032.GA9524@nevyn.them.org> <e2nup3$1t7$1@sea.gmane.org> <20060426141002.GB20166@nevyn.them.org> <e2o1hn$a4n$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e2o1hn$a4n$1@sea.gmane.org>
User-Agent: Mutt/1.5.8i
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-04/txt/msg00321.txt.bz2

On Wed, Apr 26, 2006 at 06:53:43PM +0400, Vladimir Prus wrote:
> Here's the results I get for multiple -stack-list-frames commands:
> 
>  %   cumulative   self              self     total
>  time   seconds   seconds    calls  Ts/call  Ts/call  name
>  24.18      2.50     2.50                             find_pc_sect_psymbol
>  18.28      4.39     1.89                            
> lookup_minimal_symbol_by_pc_section
>   8.03      5.22     0.83                             find_pc_sect_psymtab
>   6.48      5.89     0.67                             find_pc_sect_section
>   4.06      6.31     0.42                             dwarf2_frame_find_fde
>   3.09      6.63     0.32                             find_pc_sect_line
>   2.03      6.84     0.21                             mem_file_write
>   1.84      7.03     0.19                             printchar
> 
> I'm not sure how to interpret this data, though.

I'd definitely try to get a callgraph - either from --enable-profiling
or callgrind, whatever.  It looks like we're doing a _lot_ of
unwinding; otherwise dwarf2_frame_find_fde shouldn't be showing up.

-- 
Daniel Jacobowitz
CodeSourcery