Mirror of the gdb mailing list
 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:21:00 -0000	[thread overview]
Message-ID: <1056385560.13489.51.camel@numenor.codito.co.in> (raw)
In-Reply-To: <20030623145919.GA17274@nevyn.them.org>

hi all,

this is with respect to my previous post. i would rather like to
rephrase my question. 

since symbol lookups are not necessarily a functionality of gdbserver
(infact gdbserver would very well work with a stripped down version of
the final executable) why is it that the target_ops structure has a
member named look_up_symbols ? or am i missing something very very basic
over here. ?and the linux implementation seems to capture information
regarding threads in linux_low.c

or is it one of the cases of the implementation not being related to the
intuitive sense one tries to make out of the name of the interface. ?

regards
Ramana






  parent reply	other threads:[~2003-06-23 16:21 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 [this message]
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=1056385560.13489.51.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