From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: GDB manual: clarify lack of restrictions on 'm' packets
Date: Tue, 15 Nov 2005 17:27:00 -0000 [thread overview]
Message-ID: <8f2776cb0511150102s42abc0a7xfe9ee344ab0224b3@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
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.
[-- Attachment #2: jimb.gdb-doc-remote-protocol-m-no-alignment.patch --]
[-- Type: text/x-patch, Size: 1951 bytes --]
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
next reply other threads:[~2005-11-15 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 17:27 Jim Blandy [this message]
2005-11-16 4:47 ` Eli Zaretskii
[not found] ` <8f2776cb0511151158n20cc5636kc974bc0cf9d967c1@mail.gmail.com>
[not found] ` <uy83p6sf9.fsf@gnu.org>
[not found] ` <8f2776cb0511152223q4c1414f1l2218bc10dbdfa74e@mail.gmail.com>
2005-11-16 7:21 ` Fwd: " Jim Blandy
2005-11-16 9:14 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f2776cb0511150102s42abc0a7xfe9ee344ab0224b3@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox