From: "dodji Seketeli" <dodji@seketeli.org>
To: "dodji Seketeli" <dodji@seketeli.org>,
"Jim Blandy" <jimb@codesourcery.com>,
gdb@sourceware.org
Subject: Re: gdb very slow during 'step into'
Date: Thu, 04 Jan 2007 10:10:00 -0000 [thread overview]
Message-ID: <adeacfc10701040210p4e6be78fyf04343c71f993b67@mail.gmail.com> (raw)
In-Reply-To: <20070104032823.GA2144@nevyn.them.org>
> You said that this is a Debian system, right? Could you try using the
> system GDB, and making sure that the libc6-dbg package is installed?
I have installed the package libc2-dbg package and it does solve the problem.
So this explains why the issue appears only on debian based distros.
I am actually writing a gdb front end (yeah, another one) so I think I
will stick to the LD_BIND_NOW solution because I cannot force users to
install the libc2-dbg package. For the record, the front end I am
writting is http://home.gna.org/nemiver.
Maybe I should file a bug to debian asking if they could install
libc6-dbg as a dependancy of gdb ? Does that make sense ?
Thank you very much.
Dodji.
next prev parent reply other threads:[~2007-01-04 10:10 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
2007-01-04 10:04 ` dodji Seketeli
2007-01-04 3:28 ` Daniel Jacobowitz
2007-01-04 10:10 ` dodji Seketeli [this message]
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=adeacfc10701040210p4e6be78fyf04343c71f993b67@mail.gmail.com \
--to=dodji@seketeli.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
/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