From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18310 invoked by alias); 23 Jun 2007 21:23:46 -0000 Received: (qmail 18301 invoked by uid 22791); 23 Jun 2007 21:23:45 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 23 Jun 2007 21:23:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 6A49E9817E; Sat, 23 Jun 2007 21:23:41 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id C8D3B9817D; Sat, 23 Jun 2007 21:23:40 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1I2D5H-0000yz-NN; Sat, 23 Jun 2007 17:23:55 -0400 Date: Sat, 23 Jun 2007 21:23:00 -0000 From: Daniel Jacobowitz To: Michael Eager Cc: Eli Zaretskii , stanshebs@earthlink.net, gdb@sources.redhat.com Subject: Re: What's an annex? stratum? Message-ID: <20070623212355.GA3448@caradoc.them.org> Mail-Followup-To: Michael Eager , Eli Zaretskii , stanshebs@earthlink.net, gdb@sources.redhat.com References: <467D5FEF.7010900@eagercon.com> <467D6D1F.7090507@earthlink.net> <467D6FB8.4080909@eagercon.com> <467D87E6.2000908@eagercon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <467D87E6.2000908@eagercon.com> User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00220.txt.bz2 On Sat, Jun 23, 2007 at 01:51:50PM -0700, Michael Eager wrote: > The doc refers to a non-existent DTD file which is supposed to > describe the XML target description annex. I assumed it was obsolete. You are looking at mismatched source and manual, I assume - you didn't say what versions you were using. In the HEAD version and snapshots, gdb/features/gdb-target.dtd does exist and the documentation describes it. The most accessible copy of the online docs refers to HEAD; I wonder if we should make the manual for the last release more prominent instead. > It's not clear whether this is the same annex referenced in target.c. Annexes are auxilliary data passed to target_xfer_partial: /* Request that OPS transfer up to LEN 8-bit bytes of the target's OBJECT. The OFFSET, for a seekable object, specifies the starting point. The ANNEX can be used to provide additional data-specific information to the target. For the remote protocol, this usually means qXfer packets, like so: `qXfer:OBJECT:read:ANNEX:OFFSET,LENGTH' Read uninterpreted bytes from the target's special data area identified by the keyword OBJECT. Request LENGTH bytes starting at OFFSET bytes into the data. The content and encoding of ANNEX is specific to the object; it can supply additional details about what data to access. -- Daniel Jacobowitz CodeSourcery