From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [rfa] NEWS updates for HEAD
Date: Tue, 28 Nov 2006 22:41:00 -0000 [thread overview]
Message-ID: <20061128224123.GE2142@nevyn.them.org> (raw)
This is everything I saw which has been added since the 6.6 branch
that I meant to add to NEWS. OK?
Someone should check over NEWS for 6.6, too; I think a few things were
missed, but it will be harder to pick them out now.
--
Daniel Jacobowitz
CodeSourcery
2006-11-28 Daniel Jacobowitz <dan@codesourcery.com>
* NEWS: Mention MIPS remote autodetection, mips64 gdbserver,
"set mem inaccessible-by-default", and "set breakpoint auto-hw".
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.203
diff -u -p -r1.203 NEWS
--- NEWS 24 Nov 2006 20:19:37 -0000 1.203
+++ NEWS 28 Nov 2006 22:39:18 -0000
@@ -6,6 +6,32 @@
* The GDB remote stub, gdbserver, now has lower overhead for high
frequency signals (e.g. SIGALRM) via the QPassSignals packet.
+* GDB for MIPS targets now autodetects whether a remote target provides
+32-bit or 64-bit register values.
+
+* New commands
+
+set mem inaccessible-by-default
+show mem inaccessible-by-default
+ If the target supplies a memory map, for instance via the remote
+ protocol's "qXfer:memory-map:read" packet, setting this variable
+ prevents GDB from accessing memory outside the memory map. This
+ is useful for targets with memory mapped registers or which react
+ badly to accesses of unmapped address space.
+
+set breakpoint auto-hw
+show breakpoint auto-hw
+ If the target supplies a memory map, for instance via the remote
+ protocol's "qXfer:memory-map:read" packet, setting this variable
+ lets GDB use hardware breakpoints automatically for memory regions
+ where it can not use software breakpoints. This covers both the
+ "break" command and internal breakpoints used for other commands
+ including "next" and "finish".
+
+* New targets
+
+MIPS64 GNU/Linux (gdbserver) mips64-linux-gnu
+
* New remote packets
QPassSignals:
next reply other threads:[~2006-11-28 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:41 Daniel Jacobowitz [this message]
2006-11-29 4:13 ` Eli Zaretskii
2006-12-05 21:22 ` Daniel Jacobowitz
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=20061128224123.GE2142@nevyn.them.org \
--to=drow@false.org \
--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