From: Daniel Jacobowitz <drow@mvista.com>
To: ramana@codito.com
Cc: gdb@sources.redhat.com
Subject: Re: Problem with multiple threads using gdbserver on x86.
Date: Mon, 23 Jun 2003 15:20:00 -0000 [thread overview]
Message-ID: <20030623145919.GA17274@nevyn.them.org> (raw)
In-Reply-To: <1056380381.13489.30.camel@numenor.codito.co.in>
On Mon, Jun 23, 2003 at 08:29:42PM +0530, Ramana Radhakrishnan wrote:
> On Mon, 2003-06-23 at 18:58, Daniel Jacobowitz wrote:
> > I dunno. Probably just providing a stub for ps_get_thread_area
> > (spelling?) will be enough to make it work.
> there does not seem to be any reference to this function anywhere in the
> gdbserver code that i have. maybe i have a very old version but the
> source has not changed for the last 12 months or so for the thread-db.c
> file. just checked that on cvs. the error seems to come in
> thread_db_init() and precisely when it tries to find the new threads.
You will have to look in the source to libthread_db, which is a part of
glibc and in this case NPTL, in order to figure out why this is not
working.
Debugging libthread_db is, in general, a pain in the ass.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-23 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 12:15 Ramana Radhakrishnan
2003-06-23 14:08 ` Daniel Jacobowitz
2003-06-23 14:10 ` Ramana Radhakrishnan
2003-06-23 14:13 ` Daniel Jacobowitz
[not found] ` <oprq72f1mrocv5ka@mail.codito.co.in>
[not found] ` <20030623132811.GA30502@nevyn.them.org>
2003-06-23 15:13 ` Ramana Radhakrishnan
2003-06-23 15:20 ` Daniel Jacobowitz [this message]
2003-06-23 16:03 ` Ramana Radhakrishnan
2003-06-23 16:21 ` Ramana Radhakrishnan
2003-06-23 16:25 ` Daniel Jacobowitz
2003-06-23 16:30 ` Ramana Radhakrishnan
2003-06-23 18:35 ` 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=20030623145919.GA17274@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=ramana@codito.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