Re: MI: performance of getting stack arguments

[Vladimir Prus <ghost@cs.msu.su>]

Daniel Jacobowitz wrote:

> On Wed, Apr 26, 2006 at 06:06:26PM +0400, Vladimir Prus wrote:
>> Ok, I'll try to do this. First on -stack-list-arguments, since it's
>> pretty slow to. But, maybe I should be using callgrind (part of valgrind
>> suite) for profiling?
> 
> I've had a lot of trouble getting the valgrind tools to play nice with
> GDB; they want to debug the children too and get confused by ptrace.
> But it looks like there've been some changes and now the default is not
> to do that, so maybe it'll work better.

Ok. I'll try.

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.

- Volodya