From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-18406-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 10753 invoked by alias); 24 Jun 2004 01:55: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 10730 invoked from network); 24 Jun 2004 01:55:39 -0000
Received: from unknown (HELO fed1rmmtao11.cox.net) (68.230.241.28)
  by sourceware.org with SMTP; 24 Jun 2004 01:55:39 -0000
Received: from ip68-3-5-250.ph.ph.cox.net ([68.3.5.250])
          by fed1rmmtao11.cox.net
          (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP
          id <20040624015538.VOYY4676.fed1rmmtao11.cox.net@ip68-3-5-250.ph.ph.cox.net>
          for <gdb@sources.redhat.com>; Wed, 23 Jun 2004 21:55:38 -0400
Received: (qmail 10112 invoked from network); 24 Jun 2004 01:55:41 -0000
Received: from localhost (HELO cox.net) (127.0.0.1)
  by ip68-3-5-250.ph.ph.cox.net with SMTP; 24 Jun 2004 01:55:41 -0000
Message-ID: <40DA349C.6080607@cox.net>
Date: Thu, 24 Jun 2004 01:55:00 -0000
From: Stephen & Linda Smith <ischis2@cox.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114
MIME-Version: 1.0
To: gdb <gdb@sources.redhat.com>
CC: Kevin Buettner <kevinb@redhat.com>
Subject: shared library support hookin the remote.c
References: <40AD1DA8.3090809@cox.net>	<40AE69AB.7000004@cox.net> <20040611141424.2bed79f7@saguaro>
In-Reply-To: <20040611141424.2bed79f7@saguaro>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-06/txt/msg00244.txt.bz2

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