public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
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:30:00 -0000	[thread overview]
Message-ID: <1056386110.13489.57.camel@numenor.codito.co.in> (raw)
In-Reply-To: <20030623162335.GA20652@nevyn.them.org>

hi daniel,

> Gdbserver needs to know the location of the symbols.  The way it does
> this is by querying GDB on the host side for the addresses.

but the only piece of code within the target specific function seems to
be getting information regarding threads .maybe i am a bit dense but
this really doesnt look like querying symbol specific information from
gdb. 

The following snippet is the code from 

linux_look_up_symbols()
{
#ifdef USE_THREAD_DB
  if (using_threads)
    return;

  using_threads = thread_db_init ();
#endif
}

regards
Ramana

  reply	other threads:[~2003-06-23 16:30 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
2003-06-23 16:21               ` Ramana Radhakrishnan
2003-06-23 16:25                 ` Daniel Jacobowitz
2003-06-23 16:30                   ` Ramana Radhakrishnan [this message]
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=1056386110.13489.57.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).