From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18769 invoked by alias); 14 Jul 2004 18:30:01 -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 18755 invoked from network); 14 Jul 2004 18:30:01 -0000 Received: from unknown (HELO fed1rmmtao04.cox.net) (68.230.241.35) by sourceware.org with SMTP; 14 Jul 2004 18:30:01 -0000 Received: from ip68-3-5-250.ph.ph.cox.net ([68.3.5.250]) by fed1rmmtao04.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20040714182958.WMAG29075.fed1rmmtao04.cox.net@ip68-3-5-250.ph.ph.cox.net> for ; Wed, 14 Jul 2004 14:29:58 -0400 Received: (qmail 7543 invoked from network); 14 Jul 2004 18:29:48 -0000 Received: from localhost (HELO cox.net) (127.0.0.1) by ip68-3-5-250.ph.ph.cox.net with SMTP; 14 Jul 2004 18:29:48 -0000 Message-ID: <40F57B9C.6020704@cox.net> Date: Wed, 14 Jul 2004 18:44: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: Andrew Cagney CC: Kevin Buettner , 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> <40E0CC21.1020401@cox.net> <20040701105812.44b85b9b@saguaro> <40E5C383.7060506@gnu.org> <40E5D0AB.7010407@cox.net> <40E5E1F6.4090203@gnu.org> <40F32979.4060102@cox.net> <40F57685.7020108@gnu.org> In-Reply-To: <40F57685.7020108@gnu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00142.txt.bz2 Andrew Cagney wrote: > > So each time the inferior stops, GDB will need to re-poll for shlib > changes? That is the way I currently have it set up. There is one thing I don't understand about the F packet. How does the inferior know that it is OK to send the packet. From everything that I have read. Comunication is initiated by GDB and answered by the inferior. I didn't know that the stub could initiate a packet. If so, Do I just tack on the F packet information to the end of a currently generated packet? This is the reason I was polling. Otherwise I prefer to not poll. > > Can the stub instead generate a packet, very like the recently added F > (File I/O) indicating that the link map changed (and what)? I think I have answered this by answering the preceding question. > > The other is to have a custom xxx-shlib hooked up to inferior stopped > that queries for the stuff you describe. It could probably be tunneled > as a TARGET_OBJECT_KOD packet. > If I implement the F packet would that get rid if the need for a xxx-shlib?