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: Wed, 03 Jan 2007 19:52:00 -0000 [thread overview]
Message-ID: <m3vejnzy4m.fsf@codesourcery.com> (raw)
In-Reply-To: <adeacfc10701030114w3ff0bf5dqd0c963f3977eeab3@mail.gmail.com> (dodji Seketeli's message of "Wed, 3 Jan 2007 10:14:22 +0100")
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
"dodji Seketeli" <dodji@seketeli.org> writes:
>> 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?
>
> Wow, yes. It does eliminate the problem. Thank you !.
I'm glad that helped! But setting LD_BIND_NOW is just a workaround;
GDB ought to work properly without that. Could you apply the
following patch to GDB and see if it makes the problem go away, even
with LD_BIND_NOW left unset?
(Tested without regressions on Fedora Core 6 IA-32. I haven't been
able to reproduce the problem myself, so I'm just guessing that this
is the patch.)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: look up _dl_fixup to step over dynamic linker resolver --]
[-- Type: text/x-patch, Size: 975 bytes --]
gdb/ChangeLog:
2007-01-03 Jim Blandy <jimb@codesourcery.com>
* glibc-tdep.c (glibc_skip_solib_resolver): Look for '_dl_fixup',
then plain 'fixup'.
Index: gdb/glibc-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/glibc-tdep.c,v
retrieving revision 1.3
diff -u -r1.3 glibc-tdep.c
--- gdb/glibc-tdep.c 17 Dec 2005 22:34:00 -0000 1.3
+++ gdb/glibc-tdep.c 3 Jan 2007 19:49:17 -0000
@@ -90,8 +90,14 @@
if (resolver)
{
+ /* This is the name used in the dynamic linker at the beginning
+ of 2007. */
struct minimal_symbol *fixup
- = lookup_minimal_symbol ("fixup", NULL, objfile);
+ = lookup_minimal_symbol ("_dl_fixup", NULL, objfile);
+
+ /* This is the name used in older versions. */
+ if (! fixup)
+ fixup = lookup_minimal_symbol ("fixup", NULL, objfile);
if (fixup && SYMBOL_VALUE_ADDRESS (fixup) == pc)
return frame_pc_unwind (get_current_frame ());
next prev parent reply other threads:[~2007-01-03 19:52 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 [this message]
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=m3vejnzy4m.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