From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20304 invoked by alias); 21 May 2004 20:49:15 -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 20296 invoked from network); 21 May 2004 20:49:14 -0000 Received: from unknown (HELO fed1rmmtao01.cox.net) (68.230.241.38) by sourceware.org with SMTP; 21 May 2004 20:49:14 -0000 Received: from ip68-3-5-250.ph.ph.cox.net ([68.3.5.250]) by fed1rmmtao01.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040521204209.LDTS21007.fed1rmmtao01.cox.net@ip68-3-5-250.ph.ph.cox.net> for ; Fri, 21 May 2004 16:42:09 -0400 Received: (qmail 9479 invoked from network); 21 May 2004 20:42:10 -0000 Received: from localhost (HELO cox.net) (127.0.0.1) by ip68-3-5-250.ph.ph.cox.net with SMTP; 21 May 2004 20:42:10 -0000 Message-ID: <40AE69AB.7000004@cox.net> Date: Fri, 21 May 2004 20:49:00 -0000 From: "Stephen P. Smith" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: gdb CC: Kevin Buettner Subject: Re: shared library support References: <40AD1DA8.3090809@cox.net> In-Reply-To: <40AD1DA8.3090809@cox.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00151.txt.bz2 First I need to say that I didn't recieve the reply email from the redhat server but found the reply in the archives. Therefore if this post looks like it follows up to the wrong message you know why. KB> My recollection of the matter is that you didn't do it this way....The easiest course KB> and the preferred course are not the same though. The preferred course is to KB> write your shared library support as a solib.c backend, add some OSABI recognition KB> code for your target along with a suitable OSABI-specific tdep.c file for your target. KB> In this (latter) file, you would call some as yet to be written machinery in solib.c KB> which'd enable your target's shared library support. This is just a thumbnail KB> sketch; if you choose to go this route, I'm willing to go into much more detail KB> and even assist with writing the necessary solib.c support. In this case, and since some things have changed, I prefer to do it the correct way. I may need quite abit of direction since I this will be my first major effort as long as you don't mind. Kevin, would you please go into more detail about the solib.c support that you think is needed. One of the things, besides what you have talked about already that may need done is what do about communicating with the remote target on this issue. As far as I can tell, there isn't anything in the remote protocal for the target to let the host know (or for the host to ask) about shared libraries. But that is for a future disussion. Also would you want me to submit these changes as a series of small patches, or big ones. sps