This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RFA: GDB manual: clarify lack of restrictions on 'm' packets


This comes out of the recent discussion on gdb@:
http://sourceware.org/ml/gdb/2005-11/msg00282.html

gdb/doc/ChangeLog:
2005-11-15  Jim Blandy  <jimb@redhat.com>

	* gdb.texinfo (Packets): Clarify lack of restrictions on behavior
	of stub when processing an 'm' packet.
gdb/doc/ChangeLog:
2005-11-15  Jim Blandy  <jimb@redhat.com>

	* gdb.texinfo (Packets): Clarify lack of restrictions on behavior
	of stub when processing an 'm' packet.

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.287
diff -c -p -r1.287 gdb.texinfo
*** gdb/doc/gdb.texinfo	14 Nov 2005 03:27:22 -0000	1.287
--- gdb/doc/gdb.texinfo	15 Nov 2005 08:59:04 -0000
*************** Reserved for future use.
*** 22347,22364 ****
  @cindex @code{m} packet
  
  Read @var{length} bytes of memory starting at address @var{addr}.
! Neither @value{GDBN} nor the stub assume that sized memory transfers are
! assumed using word aligned accesses. FIXME: @emph{A word aligned memory
! transfer mechanism is needed.}
  
  Reply:
  @table @samp
  @item @var{XX@dots{}}
  @var{XX@dots{}} is mem contents. Can be fewer bytes than requested if able
! to read only part of the data.  Neither @value{GDBN} nor the stub assume
! that sized memory transfers are assumed using word aligned
! accesses. FIXME: @emph{A word aligned memory transfer mechanism is
! needed.}
  @item E@var{NN}
  @var{NN} is errno
  @end table
--- 22347,22365 ----
  @cindex @code{m} packet
  
  Read @var{length} bytes of memory starting at address @var{addr}.
! Note that @var{addr} may not be aligned to any particular boundary.
! 
! The stub need not use any particular size or alignment when gathering
! data from memory for the response; even if @var{addr} is word-aligned
! and @var{length} is a multiple of the word size, the stub is free to
! use byte accesses, or not.  For this reason, this packet may not be
! suitable for accessing memory-mapped I/O devices.
  
  Reply:
  @table @samp
  @item @var{XX@dots{}}
  @var{XX@dots{}} is mem contents. Can be fewer bytes than requested if able
! to read only part of the data.
  @item E@var{NN}
  @var{NN} is errno
  @end table

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]