Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: MI: -var-update performance
Date: Thu, 08 Jun 2006 06:22:00 -0000	[thread overview]
Message-ID: <17543.38799.972990.666337@kahikatea.snap.net.nz> (raw)
In-Reply-To: <e639fk$h5n$1@sea.gmane.org>

Vladimir Prus writes:
 > 
 > Hi,
 > I'm running into a case where -var-update takes about 2 seconds to execute.
 > There's quite a lot of varobjs, but 2 seconds is beyond any expectation.
 > 
 > Here's the profile:
 > 
 > Each sample counts as 0.01 seconds.
 >   %   cumulative   self              self     total
 >  time   seconds   seconds    calls  Ts/call  Ts/call  name
 >  22.44     70.23    70.23                             lookup_partial_symbol
 >  19.65    131.72    61.49                            
 > lookup_minimal_symbol_by_pc_section
 >  15.80    181.16    49.44                            
 > basic_lookup_transparent_type
 >  10.39    213.67    32.51                             find_pc_sect_psymtab
 >   5.25    230.11    16.45                             strcmp_iw_ordered
 >   2.50    237.93     7.82                             find_pc_sect_section
 >   1.96    244.06     6.13                             dwarf2_frame_find_fde
 >   1.88    249.94     5.89                             strcmp_iw
 >   1.21    253.72     3.78                             read_partial_die
 >   1.02    256.90     3.18                            
 > lookup_symbol_aux_psymtabs
 >   0.97    259.94     3.04                             symbol_search_name
 > 
 > 
 > 
 > Any ideas what's up? Should I try to rebuild gdb with --enable-profiling to
 > get call graph?

More generally, I think we should add a timestamp field, like Apple have, so
we can see which MI commands are using most of the time e.g.

   From: Jason Molenda <jmolenda@apple.com>
   Subject: Re: How does GDB/MI give the current frame
   Date: Thu, 15 Jul 2004 13:04:20 -0700

  (gdb)
  -interpreter-exec console-quoted up
  ~"#2  0x000321f4 in gdb_main (args=0xbffff620) at  
  ../../gdb/src/gdb/main.c:851\n"
  ~"851\t  catch_errors (captured_main, args, \"\", RETURN_MASK_ALL);\n"
  ^done,MI_HOOK_RESULT=[HOOK_TYPE="frame_changed",frame="2"],time= 
  {wallclock="0.00620",user="0.00323",system="0.00283",start="1089921236.3 
  59009",end="1089921236.365212"}
  (gdb)


-- 
Nick                                           http://www.inet.net.nz/~nickrob


      parent reply	other threads:[~2006-06-08  3:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06  7:05 Vladimir Prus
2006-06-06 12:33 ` Daniel Jacobowitz
2006-06-08  6:22 ` Nick Roberts [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17543.38799.972990.666337@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox