This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
-data-read-memory docs (Was: MI -break-info command issues)
- From: Vladimir Prus <ghost at cs dot msu dot su>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 17 Mar 2006 20:06:19 +0300
- Subject: -data-read-memory docs (Was: MI -break-info command issues)
- References: <dr5csi$bg2$1@sea.gmane.org> <drdchc$672$1@sea.gmane.org> <ud5idehd5.fsf@gnu.org>
On Friday 27 January 2006 20:00, Eli Zaretskii wrote:
> > From: Vladimir Prus <ghost@cs.msu.su>
> > 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