From: Daniel Jacobowitz <drow@mvista.com>
To: nak26 <nak26@drexel.edu>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: pthread_db innitializing error
Date: Wed, 25 Jun 2003 18:30:00 -0000 [thread overview]
Message-ID: <20030625171944.GA24093@nevyn.them.org> (raw)
In-Reply-To: <3EF9D828@webmail.drexel.edu>
On Wed, Jun 25, 2003 at 12:38:44PM -0400, nak26 wrote:
> Hi:
>
> I am fighting problems I have when trying to remotely debug multithreaded
> applications.
>
> The host machine's solib-absolute-prefix is messed up, so when I start I set
> the solib search path to look for libraries at the right places (it was
> looking at /lib/i686 instead of just in /lib). Then after hitting a breakpoint
> I need to issue shared to load the libararies.
Eh? It sounds like you're not using the right libraries at all.
solib-absolute-prefix should point to a copy of the target filesystem
layout - the target's versions of libraries. It shouldn't search /lib
at all.
> At this point on the target terminal I see this (the application is a
> multithreaded toy example):
>
> [localhost ~/src/c/threads]$ ~/.local/src/gdb-5.3/gdb/gdbserver/gdbserver
> :7000 hello_world_thread
> Process hello_world_thread created; pid = 2486
> Remote debugging from host 192.168.66.59
> gdb: error initializing thread_db library.
> gdb: error initializing thread_db library.
> gdb: error initializing thread_db library.
>
> Anybody with ideas why I am getting the error?
>
> Both host and target are IA32 RedHat 8.0s.
Probably symbol resolution is not working; most likely because you have
the wrong libpthread on the host.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-25 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 17:01 nak26
2003-06-25 18:30 ` Daniel Jacobowitz [this message]
2003-06-25 18:31 nak26
2003-06-26 4:58 ` Daniel Jacobowitz
2003-06-26 14:34 nak26
2003-06-26 14:44 ` 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=20030625171944.GA24093@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=nak26@drexel.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).