From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13447 invoked by alias); 18 Jun 2007 19:32:02 -0000 Received: (qmail 13437 invoked by uid 22791); 18 Jun 2007 19:32:02 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 18 Jun 2007 19:32:00 +0000 Received: (qmail 10679 invoked from network); 18 Jun 2007 19:31:58 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Jun 2007 19:31:58 -0000 To: gdb-patches@sourceware.org Cc: Ulrich Weigand , Pedro Alves Subject: Re: [rfc] Shared libraries over the remote protocol, take two References: <20070618150211.GA23415@caradoc.them.org> From: Jim Blandy Date: Mon, 18 Jun 2007 19:32:00 -0000 In-Reply-To: <20070618150211.GA23415@caradoc.them.org> (Daniel Jacobowitz's message of "Mon, 18 Jun 2007 11:02:11 -0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00343.txt.bz2 Daniel Jacobowitz writes: > Here is a new attempt at remote shared library events. The major > protocol changes since last time are the elimination of load/unload > events (just query the whole list again), the use of target objects > (so that this can be used more easily for other targets, like AIX) > , and the use XML (because I had to both escape the entire message > and then the library name - my rule of thumb is that when I need to > invent a new way to escape special characters, I should probably use > XML, since it offers a standard way to do that "for free"). > > I have tested this on native Windows and using a Windows gdbserver, > both with the patch coming up next. It seems to work fine. It's also > much simpler to explain how it works, and about half the lines of code > of the previous version. With the following DTD: there's no way to have several segments at different offsets, because segments aren't allowed to have names. Shouldn't segments have a name attribute?