From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: ramana@codito.com, gdb@sources.redhat.com
Subject: Re: Problem with multiple threads using gdbserver on x86.
Date: Mon, 23 Jun 2003 16:03:00 -0000 [thread overview]
Message-ID: <1056384479.13489.38.camel@numenor.codito.co.in> (raw)
In-Reply-To: <20030623145919.GA17274@nevyn.them.org>
On Mon, 2003-06-23 at 20:29, Daniel Jacobowitz wrote:
> 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.
>
Thanx for the info. will look into the same
.
but that still does not answer my question regarding
linux_look_up_symbols.. I was under the
impression that looking up symbols was a file format / debug format
specific thing and not an OS specific functionality and would like to
know the reason behind having a function like look_up_symbol in the
target_ops structure and seem to use it to initialize the thread
information in the implementation ?
regards
Ramana
--
God made machine language - the rest is the work of man.
next prev parent reply other threads:[~2003-06-23 16:03 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
2003-06-23 16:03 ` Ramana Radhakrishnan [this message]
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=1056384479.13489.38.camel@numenor.codito.co.in \
--to=ramana.radhakrishnan@codito.com \
--cc=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