From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16938 invoked by alias); 23 Jun 2003 16:25:35 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 13867 invoked from network); 23 Jun 2003 16:24:16 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 23 Jun 2003 16:24:16 -0000 Received: from dsl093-172-017.pit1.dsl.speakeasy.net ([66.93.172.17] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19UU7L-0004bL-00; Mon, 23 Jun 2003 11:24:31 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19UU6R-0005NT-00; Mon, 23 Jun 2003 12:23:35 -0400 Date: Mon, 23 Jun 2003 16:25:00 -0000 From: Daniel Jacobowitz To: ramana@codito.com Cc: gdb@sources.redhat.com Subject: Re: Problem with multiple threads using gdbserver on x86. Message-ID: <20030623162335.GA20652@nevyn.them.org> Mail-Followup-To: ramana@codito.com, gdb@sources.redhat.com 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> <20030623132811.GA30502@nevyn.them.org> <1056380381.13489.30.camel@numenor.codito.co.in> <20030623145919.GA17274@nevyn.them.org> <1056385560.13489.51.camel@numenor.codito.co.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1056385560.13489.51.camel@numenor.codito.co.in> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-06/txt/msg00452.txt.bz2 On Mon, Jun 23, 2003 at 09:56:01PM +0530, Ramana Radhakrishnan wrote: > 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. ? 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. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer