From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19295 invoked by alias); 17 Mar 2006 17:06:38 -0000 Received: (qmail 19265 invoked by uid 22791); 17 Mar 2006 17:06:36 -0000 X-Spam-Check-By: sourceware.org Received: from zigzag.lvk.cs.msu.su (HELO zigzag.lvk.cs.msu.su) (158.250.17.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 17:06:34 +0000 Received: from Debian-exim by zigzag.lvk.cs.msu.su with spam-scanned (Exim 4.50) id 1FKIPB-0001hC-DO for gdb@sources.redhat.com; Fri, 17 Mar 2006 20:06:30 +0300 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by zigzag.lvk.cs.msu.su with esmtp (Exim 4.50) id 1FKIP6-0001fw-5F; Fri, 17 Mar 2006 20:06:20 +0300 From: Vladimir Prus To: Eli Zaretskii Subject: -data-read-memory docs (Was: MI -break-info command issues) Date: Fri, 17 Mar 2006 17:07:00 -0000 User-Agent: KMail/1.7.2 References: In-Reply-To: Cc: gdb@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603172006.19705.ghost@cs.msu.su> 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-03/txt/msg00127.txt.bz2 On Friday 27 January 2006 20:00, Eli Zaretskii wrote: > > From: Vladimir Prus > > Date: Fri, 27 Jan 2006 17:59:56 +0300 > > > > > The first memory address to be displayed on the next/previous > > > row or page is given as the values of the fields `next-row' and > > > `prev-row', `next-page' and `prev-page', respectively. > > > > This misses the definition of 'page' and definition of 'next'/'prev'. > > Based on looking on the code, I could suggest this: > > > > Assuming memory is a sequence of "pages", where each "page" is > > "total-nr" bytes the "next-page" is the address of page directly after > > the page returned by -data-read-memory, and "prev-page" is the address of > > the first byte of the directly preceding page. Likewise, assuming memory > > is a sequence of rows, where each row is word_size*nr_cols bytes, > > "next-row" is the address of the row directly after the first one in the > > -data-read-memory output (that is, the address of the second row of the > > output, if there's second row). The "prev-row" is the start address of > > the row directly preceding the first output row. > > Thanks, but this is too wordy. I will try to come up with some > suitable definition of `page'. (I don;t think that `previous' needs a > definition; perhaps you meant that `previous page' needs it.) Eli, have you had a chance to think about a better documentation for this? Thanks, Volodya