From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29294 invoked by alias); 29 Jun 2004 01:55:38 -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 29071 invoked from network); 29 Jun 2004 01:55:32 -0000 Received: from unknown (HELO fed1rmmtao05.cox.net) (68.230.241.34) by sourceware.org with SMTP; 29 Jun 2004 01:55:32 -0000 Received: from ip68-3-5-250.ph.ph.cox.net ([68.3.5.250]) by fed1rmmtao05.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040629015530.LITR26142.fed1rmmtao05.cox.net@ip68-3-5-250.ph.ph.cox.net> for ; Mon, 28 Jun 2004 21:55:30 -0400 Received: (qmail 6299 invoked from network); 29 Jun 2004 01:55:46 -0000 Received: from localhost (HELO cox.net) (127.0.0.1) by ip68-3-5-250.ph.ph.cox.net with SMTP; 29 Jun 2004 01:55:46 -0000 Message-ID: <40E0CC21.1020401@cox.net> Date: Tue, 29 Jun 2004 01:56:00 -0000 From: Stephen & Linda Smith User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 MIME-Version: 1.0 To: Kevin Buettner CC: gdb@sources.redhat.com Subject: Re: shared library support hookin the remote.c References: <40AD1DA8.3090809@cox.net> <40AE69AB.7000004@cox.net> <20040611141424.2bed79f7@saguaro> <40DA349C.6080607@cox.net> <20040628134303.20e1cff0@saguaro> <40E09084.70108@cox.net> <20040628172120.2844044d@saguaro> In-Reply-To: <20040628172120.2844044d@saguaro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00283.txt.bz2 Kevin Buettner wrote: > How does the remote target communicate the necessary details to GDB > >then? > >It sounds to me as though you want to add the hook so that you can add >a private protocol extension. > >IMO, it's better to hash out the details of a public remote protocol >extension for shared library support. > That would be my preference, but I haven't figured out a generic way. Here is the basic problem is that the remote protocol has no notion of shared libraries or of segments (TEXT, BSS, DATA, etc). Can someone on this list think of a generic way of getting this data? A second problem is that the number and names of the segments doesn't appear to be consistent. It was for this reason that I was thinking of making the protocol a target specific one that supports the solib interface. >... I'd like to first understand how communication of shared library information >between GDB and the stub is accomplished and what the protocol looks >like. > I assume you don't mean how the published protocol works. What I didn't in the passed, was to use a q packet. If I read the spec correctly was to use that packet type to find out if there were any libraries and to find out the segment addersses. I don't mind making it a public interface, but from the conversation three years ago, I got the idea that the maintainers weren't especially keen on making it part of the general (i.e remote.c) code base.