From: Jim Blandy <jimb@codesourcery.com>
To: "dodji Seketeli" <dodji@seketeli.org>
Cc: gdb@sourceware.org
Subject: Re: gdb very slow during 'step into'
Date: Tue, 02 Jan 2007 19:29:00 -0000 [thread overview]
Message-ID: <m3zm91kz07.fsf@codesourcery.com> (raw)
In-Reply-To: <adeacfc10701020723g245481a7r7848b00db337ac00@mail.gmail.com> (dodji Seketeli's message of "Tue, 2 Jan 2007 16:23:52 +0100")
"dodji Seketeli" <dodji@seketeli.org> writes:
> Hello gdb hackers and users,
>
> First of all, I would like to wish a happy new year to you and your families.
> I hope this year will be full of achievements (again) for gdb people.
>
> Now the real meat of my post :-)
>
> I have noticed that gdb was very slow (taking 100% of CPU during
> several tens of seconds) when I step into some functions (with the
> step command, on the cli interface).
>
> I am not sure, but I think it happens when I step into functions that
> are defined in certain shared libraries. Once in the function,
> subsequent steping into functions of the same library are okay. Once
> out of the library, stepping into a function of that library can be
> slow again.
If you set the environment variable LD_BIND_NOW to a non-empty value
before running your program (use GDB's 'set env' command), does that
eliminate the slow steps?
next prev parent reply other threads:[~2007-01-02 19:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 15:24 dodji Seketeli
2007-01-02 19:29 ` Jim Blandy [this message]
2007-01-02 19:31 ` Daniel Jacobowitz
2007-01-02 19:48 ` Jim Blandy
2007-01-02 21:39 ` Mark Kettenis
2007-01-02 22:59 ` Andreas Schwab
2007-01-02 23:45 ` Jim Blandy
2007-01-02 23:57 ` Daniel Jacobowitz
2007-01-03 15:03 ` Andreas Schwab
2007-01-03 9:14 ` dodji Seketeli
2007-01-03 19:52 ` Jim Blandy
2007-01-03 19:59 ` Smith, Stephen (SWCOE)
2007-01-03 21:19 ` Jim Blandy
2007-01-03 20:59 ` Andreas Schwab
2007-01-03 21:17 ` Jim Blandy
2007-01-03 21:58 ` dodji Seketeli
2007-01-03 23:37 ` Jim Blandy
2007-01-03 23:42 ` Daniel Jacobowitz
2007-01-04 0:00 ` Jim Blandy
2007-01-04 10:04 ` dodji Seketeli
2007-01-04 3:28 ` Daniel Jacobowitz
2007-01-04 10:10 ` dodji Seketeli
2007-01-04 13:53 ` Daniel Jacobowitz
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=m3zm91kz07.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=dodji@seketeli.org \
--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