Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH] Document non-8-bits-addressable support in NEWS
Date: Wed, 26 Aug 2015 20:17:00 -0000	[thread overview]
Message-ID: <1440620235-24006-1-git-send-email-simon.marchi@ericsson.com> (raw)

I think it would be a good idea to document that gdb now has (basic)
support to read/write memory on architectures with non-8-bits memory.
Hopefully somebody will see it and say "Hey!  We can now (more easily)
port GDB to our strange DSP that has 32-bits-addressable memory!" and do
it.

gdb/ChangeLog:

	* NEWS: Document support for non-8-bits addressable memory.
---
 gdb/NEWS | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index 49c4a11..ed4d968 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -48,6 +48,11 @@ show remote multiprocess-extensions-packet
   target mon2000	mon2000 ROM monitor
   target ppcbug		PPCBUG ROM monitor for PowerPC
 
+* Support for reading/writing memory and extracting values on architectures
+  with non-8-bits-addressable memory.  A 16-bits-addressable memory, for
+  example, is one for which each address holds a 16-bits value (as opposed to
+  the more common 8-bits).
+
 *** Changes in GDB 7.10
 
 * Support for process record-replay and reverse debugging on aarch64*-linux*
-- 
2.1.4


             reply	other threads:[~2015-08-26 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 20:17 Simon Marchi [this message]
2015-08-27  2:38 ` Eli Zaretskii
2015-08-27 13:34   ` Simon Marchi
2015-08-27 14:11     ` Paul_Koning
2015-08-27 14:26       ` Simon Marchi
2015-08-27 15:05         ` Simon Marchi
2015-08-27 15:13           ` Paul_Koning
2015-08-27 15:39           ` Eli Zaretskii
2015-08-28 19:37             ` Simon Marchi

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=1440620235-24006-1-git-send-email-simon.marchi@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    /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