From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Andreas Schwab <schwab@suse.de>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb@sourceware.org
Subject: Re: gdb very slow during 'step into'
Date: Tue, 02 Jan 2007 23:57:00 -0000 [thread overview]
Message-ID: <20070102235655.GA26077@nevyn.them.org> (raw)
In-Reply-To: <m3ps9xdmc7.fsf@codesourcery.com>
On Tue, Jan 02, 2007 at 03:45:44PM -0800, Jim Blandy wrote:
>
> Andreas Schwab <schwab@suse.de> writes:
> > Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> >
> >> Do it might very well be that the lookup for "_dl_runtime_resolve" or
> >> "fixup" fails, especially on a system whithout debug info for glibc.
> >
> > In current glibc versions the function is called _dl_fixup anyway.
>
> I think those are two different things:
>
> $ nm /lib/ld-linux.so.2 | grep _dl_fixup
> 0087ea30 t _dl_fixup
> $ nm /lib/ld-linux.so.2 | grep _dl_runtime_resolve
> 00883ec0 t _dl_runtime_resolve
He's talking about fixup, not about _dl_runtime_resolve. They're
different things, IIRC.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-02 23:57 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 [this message]
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=20070102235655.GA26077@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=mark.kettenis@xs4all.nl \
--cc=schwab@suse.de \
/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