From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: gdb@sources.redhat.com, libc-alpha@sources.redhat.com
Cc: Peter.Barada@motorola.com
Subject: Trouble with gdbserver from gdb-5.3, glibc-2.3.2 on ppc32
Date: Tue, 09 Sep 2003 20:32:00 -0000 [thread overview]
Message-ID: <200309092031.h89KVsI30886@hyper.wm.sps.mot.com> (raw)
I'm trying to bring up gdbserver2 on an ppc32 embedded linux platform, and
I'm running in to the following message. It doesn't alway appear, so
it has me pretty confused....
sh-2.05b# cat /proc/version
Linux version 2.4.21-rc1 (pbarada@hyper) (gcc version 3.3.1) #21 Tue Sep 9 15:43
sh-2.05b# gdbserver2 :3001 /usr/local/bin/page.strip -m16m -J < /dev/lp0
Process /usr/local/bin/page.strip created; pid = 35
Remote debugging from host 10.1.1.2
gdb: error initializing thread_db library.
I modified gdbserver/thread-db.c::thread_db_init to print the value of
the err that is returned form td_ta_new, and the result is 0x16 which
if I read glibc-2.3.2/linuxthreads_db/thread_db.h correctly, the 0x16
returned from td_ta_new() is TD_VERSION which means the version of
libpthread doesn't match the version of libthread_db.
If I look in gdb for the type of TD_VERSION I don't see TD_VERSION
even thos I see it in linuxthreads_db/thread_db.h:
(gdb) ptype TD_OK
type = enum {TD_OK, TD_ERR, TD_NOTHR, TD_NOSV, TD_NOLWP, TD_BADPH, TD_BADTH, TD_BADSH,
TD_BADTA, TD_BADKEY, TD_NOMSG, TD_NOFPREGS, TD_NOLIBTHREAD, TD_NOEVENT,
TD_NOCAPAB, TD_DBERR, TD_NOAPLIC, TD_NOTSD, TD_MALLOC, TD_PARTIALREG, TD_NOXREGS}
(gdb) ptype TD_VERSION
No symbol "TD_VERSION" in current context.
My question is how I can tell why gdbserver believes that the verion
of libpthread.so.0 doesn't match the version of libthread_db.so.1?
Whath options to readelf do I need?
execution doesn't work after this (i.e. 'inf thr' doesn't show me my
thread, etc). I'm wondering if there's a deeper problem...
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(A Motorola Company) 781-270-0193 (fax)
next reply other threads:[~2003-09-09 20:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 20:32 Peter Barada [this message]
2003-09-09 20:46 ` Roland McGrath
2003-09-09 21:15 ` Peter Barada
2003-09-09 21:24 ` Roland McGrath
2003-09-09 21:23 ` Daniel Jacobowitz
2003-09-09 21:30 ` Daniel Jacobowitz
2003-09-09 21:39 ` Roland McGrath
2003-09-09 21:40 ` Daniel Jacobowitz
2003-09-10 0:18 ` Peter Barada
2003-09-10 17:41 ` Peter Barada
2003-09-10 18:58 ` Peter Barada
2003-09-10 0:34 ` Peter Barada
2003-09-10 0:49 ` Dan Kegel
2003-09-10 0:53 ` Peter Barada
2003-09-09 21:45 ` Dan Kegel
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=200309092031.h89KVsI30886@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=Peter.Barada@motorola.com \
--cc=gdb@sources.redhat.com \
--cc=libc-alpha@sources.redhat.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