* target.c, target.h: Add "set remotedebug" command.

[binutils-gdb.git] / gdb / NEWS

diff --git a/gdb/NEWS b/gdb/NEWS
index b77a1ea3e22e18b07ad476a7fee52eba4bb51c4f..75d3d4261ee81de6f251734dae169e35ac591d68 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,6 +1,38 @@
                What has changed since GDB-3.5?
                (Organized release by release)
 
+The "set remotedebug" option is now consistent between the mips remote
+target, remote targets using the gdb-specific protocol, and the 88k
+bug monitor.  It is now an integer specifying a debug level (normally
+0 or 1, but 2 means more debugging info for the mips target).
+
+*** Changes in GDB-4.10:
+
+ * User visible changes:
+
+Remote debugging using the GDB-specific (`target remote') protocol now
+supports the `load' command.  This is only useful if you have some
+other way of getting the stub to the target system, and you can put it
+somewhere in memory where it won't get clobbered by the download.
+
+Filename completion now works.
+
+When run under emacs mode, the "info line" command now causes the
+arrow to point to the line specified.  Also, "info line" prints
+addresses in symbolic form (as well as hex).
+
+All vxworks based targets now support a user settable option, called
+vxworks-timeout.  This option represents the number of seconds gdb
+should wait for responses to rpc's.  You might want to use this if
+your vxworks target is, perhaps, a slow software simulator or happens
+to be on the far side of a thin network line.
+
+ * DEC alpha support
+
+This release contains support for using a DEC alpha as a GDB host for
+cross debugging.  Native alpha debugging is not supported yet.
+
+
 *** Changes in GDB-4.9:
 
  * Testsuite