From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88948 invoked by alias); 10 Apr 2015 17:42:09 -0000 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 Received: (qmail 88302 invoked by uid 89); 10 Apr 2015 17:42:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout29.012.net.il Received: from mtaout29.012.net.il (HELO mtaout29.012.net.il) (80.179.55.185) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Apr 2015 17:42:07 +0000 Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NML00C00PYM3600@mtaout29.012.net.il> for gdb-patches@sourceware.org; Fri, 10 Apr 2015 20:39:54 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NML004CDQEHDG80@mtaout29.012.net.il>; Fri, 10 Apr 2015 20:39:54 +0300 (IDT) Date: Fri, 10 Apr 2015 17:42:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 0/7] Support reading/writing memory on architectures with non 8-bits bytes In-reply-to: <5527F3BC.3030005@ericsson.com> To: Simon Marchi Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <831tjrubgy.fsf@gnu.org> References: <1428522979-28709-1-git-send-email-simon.marchi@ericsson.com> <83d23dg1bd.fsf@gnu.org> <55269D1A.3080902@ericsson.com> <83vbh5e04f.fsf@gnu.org> <5526E87D.3020109@ericsson.com> <838ue0v1vy.fsf@gnu.org> <5527F3BC.3030005@ericsson.com> X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00401.txt.bz2 > Date: Fri, 10 Apr 2015 12:01:00 -0400 > From: Simon Marchi > CC: > > > I want GDB to be agnostic, as far as possible, to the size of 1 unit > > of memory. Ideally, one unit will start as one unit in user-level > > commands, pass all the way down to the target level, which should know > > what one unit means. > > I totally agree with you, and I believe that's the idea you'll find implemented > in the patches. The length is always passed in "units of memory" of whatever you > are trying to read or write. The only thing is that I called a "unit of memory" > a "byte", which seems the friction point. If it's just a wording issue, it can > be changed easily. I just don't know what succinct term to use. W could use the terminology that is already in use: "half-words" for 16 bits and "words" for 32 bits. Would that be OK? > Ok, so if I understand correctly, you would be fine if the -data-read-memory-bytes > command accepted a length in number of memory units, as long as this unit is not > called a byte. Yes. Though it's unfortunate that the name of the command explicitly mentions "bytes".