Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Arne Steinarson <asteinarson@yahoo.se>
Cc: gdb@sourceware.org
Subject: Re: Performance, stepping into source for shared libs
Date: Mon, 02 Jul 2007 00:04:00 -0000	[thread overview]
Message-ID: <18056.16647.432000.944702@kahikatea.snap.net.nz> (raw)
In-Reply-To: <168749.90326.qm@web25413.mail.ukl.yahoo.com>

Arne Steinarson writes:
 > I have a C++ app with just a small main.cpp. However
 > it links into large libraries (GTK and framework on
 > top of GTK, running i386 Linux).
 > 
 > Most times when I open the app in GDB I will have
 > quite a delay when stepping into a lower function the
 > first time. CPU usage goes to 100% and it takes
 > between 10 and 60 seconds before I can see the new
 > source line. The next time stepping into the same
 > function, it happens without delay.
 > 
 > Stepping into a new function in another source file
 > (possibly in the same directory as the last one) I
 > again have the long delay.
 > 
 > It seems to happen mostly with functions in shared
 > libraries.
 > 
 > First I thought it was the IDE (Eclipse) to blame. So
 > I tried in GDB standalone, command line version. Same
 > delay!
 > 
 > Is there some way to reduce these waits?

What happens if you do

  (gdb) set auto-solib-add off

first?

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


  reply	other threads:[~2007-07-02  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 23:34 Arne Steinarson
2007-07-02  0:04 ` Nick Roberts [this message]
2007-07-02  1:42 ` Daniel Jacobowitz
2007-07-02  8:57 Arne Steinarson

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=18056.16647.432000.944702@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=asteinarson@yahoo.se \
    --cc=gdb@sourceware.org \
    /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