From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21960 invoked by alias); 22 Jun 2006 08:42:02 -0000 Received: (qmail 21948 invoked by uid 22791); 22 Jun 2006 08:42:01 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 Jun 2006 08:41:58 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FtKl9-0002D9-I8 for gdb@sources.redhat.com; Thu, 22 Jun 2006 10:41:55 +0200 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 22 Jun 2006 10:41:55 +0200 Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 22 Jun 2006 10:41:55 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: [remote] RFC: Replace qPart with qXfer Date: Thu, 22 Jun 2006 09:05:00 -0000 Message-ID: References: <20060622031731.GA26722@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.8.2 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00181.txt.bz2 Daniel Jacobowitz wrote: > `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. Why do we need OBJECT+ANNEX addressing and opposed to just OBJECT? If 'OBJECT' is just a string, can't we push anything in it, without needed extra level of addressing? - Volodya