Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Savoiu <savoiu@ics.uci.edu>
To: gdb@sources.redhat.com
Subject: Re: Improving GDB startup time with large programs
Date: Mon, 03 May 2004 02:49:00 -0000	[thread overview]
Message-ID: <200405021948.50571.savoiu@ics.uci.edu> (raw)
In-Reply-To: <20040502224944.847584B104@berman.michael-chastain.com>

>> How do I profile gdb?
>
>When you build gdb, configure as normal.
>Then use this command to build:

Here's what I got (the most significant stuff) with g++ 3.2. Seems that the number of symbols is the culprit.

Nick

--------------------------------

Flat profile:

Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total           
 time   seconds   seconds    calls   s/call   s/call  name    
 18.61      1.93     1.93  2013562     0.00     0.00  hash
 13.55      3.33     1.41  9757458     0.00     0.00  strcmp_iw_ordered
 11.86      4.57     1.23  2310964     0.00     0.00  htab_hash_string
  9.55      5.55     0.99  6206314     0.00     0.00  read_partial_die
  4.97      6.07     0.52  1906172     0.00     0.00  bcache_data
  3.38      6.42     0.35  5101168     0.00     0.00  read_indirect_string
  3.33      6.76     0.34 23770551     0.00     0.00  read_attribute_value
  3.18      7.09     0.33   948693     0.00     0.00  d_print_comp
  2.60      7.37     0.27  2032858     0.00     0.00  htab_find_slot_with_hash
  1.59      7.53     0.17  9203512     0.00     0.00  read_unsigned_leb128
  1.54      7.69     0.16 23770551     0.00     0.00  read_attribute
  1.25      7.82     0.13   256652     0.00     0.00  find_last_component
  1.25      7.95     0.13   131142     0.00     0.00  msymbol_hash_iw
  1.16      8.07     0.12  6643402     0.00     0.00  dwarf2_lookup_abbrev
  1.16      8.19     0.12  3934670     0.00     0.00  d_make_comp
  1.06      8.30     0.11  1906172     0.00     0.00  add_psymbol_to_list
  0.96      8.40     0.10    89224     0.00     0.00  cp_find_first_component_aux
  0.87      8.49     0.09 19615690     0.00     0.00  symbol_natural_name
  0.87      8.58     0.09 12864595     0.00     0.00  bfd_getl32
  0.87      8.67     0.09     1699     0.00     0.00  scan_partial_symbols
  0.77      8.75     0.08  2032858     0.00     0.00  symbol_set_names
  0.68      8.82     0.07 11166899     0.00     0.00  read_1_byte


  parent reply	other threads:[~2004-05-03  2:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-02 22:49 Michael Elizabeth Chastain
2004-05-02 23:11 ` Nick Savoiu
2004-05-03  2:49 ` Nick Savoiu [this message]
2004-05-03 17:17   ` Nick Savoiu
2004-05-04 19:44   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03  3:39 Michael Elizabeth Chastain
2004-05-03  1:56 Michael Elizabeth Chastain
2004-05-03 15:00 ` Andrew Cagney
2004-05-02 22:12 Nick Savoiu

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=200405021948.50571.savoiu@ics.uci.edu \
    --to=savoiu@ics.uci.edu \
    --cc=gdb@sources.redhat.com \
    /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