From: Kevin Buettner <kevinb@redhat.com>
To: Miah Gregory <miah@picsel.com>, gdb@sources.redhat.com
Subject: Re: gdb/threading under arm-linux
Date: Wed, 13 Mar 2002 09:36:00 -0000 [thread overview]
Message-ID: <1020313173614.ZM29206@localhost.localdomain> (raw)
In-Reply-To: Miah Gregory <miah@picsel.com> "Re: gdb/threading under arm-linux" (Mar 13, 1:11pm)
On Mar 13, 1:11pm, Miah Gregory wrote:
> Ok, I managed to build enough of libc 2.2.3 in order to get the required
> libthread_db.so.1 library, and I then installed that in /lib.
>
> With the 20020305 snapshot, I get all the same problems. Is there a simple
> way to find out whether gdb is trying to use that library?
Find out the GDB's pid and then do ``cat /proc/PID/maps'' (or some such)
to see which libraries are loaded and at which addresses they reside.
Chances are that you'll end up needing to use gdb to debug itself to find
out why the necessary library is not getting loaded, but it's certainly
possible that it's being loaded, but some critical symbol is not being
found by a dlsym() call. (See Daniel's suggestion.)
BTW, from your glibc build, you should install both libthread_db.so.1 as
well as the corresponding libpthread.so.0. If you've only installed one
of them, it's possible that there's some mismatch which prevents gdb from
working properly.
Kevin
prev parent reply other threads:[~2002-03-13 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 5:39 Miah Gregory
2002-03-05 7:35 ` Daniel Jacobowitz
2002-03-06 1:45 ` Miah Gregory
2002-03-06 1:51 ` Miah Gregory
2002-03-06 17:32 ` Michael Snyder
2002-03-13 5:13 ` Miah Gregory
[not found] ` <20020306110033.A14410@nevyn.them.org>
2002-03-13 5:12 ` Miah Gregory
2002-03-13 9:09 ` Daniel Jacobowitz
2002-03-13 9:44 ` Miah Gregory
2002-03-13 9:50 ` Daniel Jacobowitz
2002-03-13 9:36 ` Kevin Buettner [this message]
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=1020313173614.ZM29206@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=miah@picsel.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