From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-14498-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 7404 invoked by alias); 23 Jun 2003 16:21:40 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 6791 invoked from network); 23 Jun 2003 16:21:28 -0000
Received: from unknown (HELO calvin.codito.com) (203.197.87.98)
  by sources.redhat.com with SMTP; 23 Jun 2003 16:21:28 -0000
Received: from numenor.codito.co.in (numenor.codito.co.in [192.168.100.52])
	by calvin.codito.com (8.12.5/8.12.5) with ESMTP id h5NGIghk007929;
	Mon, 23 Jun 2003 21:49:02 +0530
Subject: Re: Problem with multiple threads using gdbserver on x86.
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
Reply-To: ramana@codito.com
To: Daniel Jacobowitz <drow@mvista.com>
Cc: ramana@codito.com, gdb@sources.redhat.com
In-Reply-To: <20030623145919.GA17274@nevyn.them.org>
References: <1056365816.1389.20.camel@numenor.codito.co.in>
	 <20030623124618.GA24330@nevyn.them.org>
	 <1056373839.13118.2.camel@numenor.codito.co.in>
	 <20030623131606.GA25130@nevyn.them.org>
	 <oprq72f1mrocv5ka@mail.codito.co.in>
	 <20030623132811.GA30502@nevyn.them.org>
	 <1056380381.13489.30.camel@numenor.codito.co.in>
	 <20030623145919.GA17274@nevyn.them.org>
Content-Type: text/plain
Organization: Codito Technologies
Message-Id: <1056385560.13489.51.camel@numenor.codito.co.in>
Mime-Version: 1.0
Date: Mon, 23 Jun 2003 16:21:00 -0000
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-06/txt/msg00451.txt.bz2

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