From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13123 invoked by alias); 28 Jun 2004 20:43:10 -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 13115 invoked from network); 28 Jun 2004 20:43:09 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 28 Jun 2004 20:43:09 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5SKh9e3022217 for ; Mon, 28 Jun 2004 16:43:09 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5SKh9020465; Mon, 28 Jun 2004 16:43:09 -0400 Received: from localhost.localdomain (vpn50-37.rdu.redhat.com [172.16.50.37]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id i5SKh8OD006151; Mon, 28 Jun 2004 16:43:08 -0400 Received: from saguaro (saguaro.lan [192.168.64.2]) by localhost.localdomain (8.12.11/8.12.10) with SMTP id i5SKh35O012641; Mon, 28 Jun 2004 13:43:03 -0700 Date: Mon, 28 Jun 2004 21:44:00 -0000 From: Kevin Buettner To: Stephen & Linda Smith Cc: gdb Subject: Re: shared library support hookin the remote.c Message-Id: <20040628134303.20e1cff0@saguaro> In-Reply-To: <40DA349C.6080607@cox.net> References: <40AD1DA8.3090809@cox.net> <40AE69AB.7000004@cox.net> <20040611141424.2bed79f7@saguaro> <40DA349C.6080607@cox.net> Organization: Red Hat Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00278.txt.bz2 On Wed, 23 Jun 2004 18:55:40 -0700 Stephen & Linda Smith wrote: > I have been trying to decide how to hook the solib support into the > remote protocol and think that what is needed is a pointer to a > function in remote.c. > > Initially the pointer would be initailized to null (zero) and > wouldn't be used unless the solib supporting code initialized it to > point to one of target specific functions. The reason I came up > with this idea is that the data that is needed by solib would in > general not be the same between targets. Also this would keep the > code that is to handle this extension out of the remote.c file which > is general in nature. > > With this resolved I think I can start coding (starting by adding > this variable to the tree). It doesn't make much sense to write the > solib support if I can't get the data out of the remote target. > > What do you think I think we need more detail. Which functions in remote.c would be affected? What would the interface look like and how would it be used? Also, please note that I am not the maintainer of remote.c... Kevin