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: Thu, 04 Jan 2007 00:00:00 -0000 [thread overview]
Message-ID: <m31wmbvewn.fsf@codesourcery.com> (raw)
In-Reply-To: <20070103234226.GA29136@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 3 Jan 2007 18:42:26 -0500")
Daniel Jacobowitz <drow@false.org> writes:
> On Wed, Jan 03, 2007 at 03:37:53PM -0800, Jim Blandy wrote:
>> Is /lib/ld-linux.so.2 normally installed stripped on your system? If
>> GDB can't find the address of the 'fixup' function, then it can't do
>> anything but single-step through the dynamic linker as it looks up the
>> symbol, which is where we're guessing you're spending your time.
>
> Yes, generally ld.so is installed stripped on Debian.
Hmm. That kind of scuttles that strategy for skipping the resolver
quickly, then, doesn't it. Unless someone has a better idea, I guess
setting LD_BIND_NOW is the best solution.
next prev parent reply other threads:[~2007-01-04 0:00 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
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 [this message]
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=m31wmbvewn.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