public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] gdb/NEWS: Move entries about MI v3 and multi-loc breakpoints after GDB 8.3
@ 2019-09-20 23:23 Joel Brobecker
  0 siblings, 0 replies; only message in thread
From: Joel Brobecker @ 2019-09-20 23:23 UTC (permalink / raw)
  To: gdb-cvs

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5a3a0d6304b400f55d60b2e9199da04fe1c7d8e4

commit 5a3a0d6304b400f55d60b2e9199da04fe1c7d8e4
Author: Joel Brobecker <brobecker@adacore.com>
Date:   Fri Sep 20 16:23:15 2019 -0700

    gdb/NEWS: Move entries about MI v3 and multi-loc breakpoints after GDB 8.3
    
    This is a followup on the following commit...
    
        commit b4be1b0648608a2578bbed39841c8ee411773edd
        Date:   Wed Mar 13 15:13:03 2019 -0400
        Subject: Fix MI output for multi-location breakpoints
    
    ... which mistakenly added NEWS entries in the "in gdb-8.3" section,
    rather than in the "since gdb-8.3" one.
    
    gdb/ChangeLog:
    
    	* NEWS: Move entries about default MI version now being
            version 3, and about the GDB/MI fix for multi-location
            breakpoints to the "since GDB 8.3" section.

Diff:
---
 gdb/ChangeLog |  6 ++++++
 gdb/NEWS      | 28 ++++++++++++++--------------
 2 files changed, 20 insertions(+), 14 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 5ac98cd..67aba3e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,11 @@
 2019-09-20  Joel Brobecker  <brobecker@adacore.com>
 
+	* NEWS: Move entries about default MI version now being
+	version 3, and about the GDB/MI fix for multi-location
+	breakpoints to the "since GDB 8.3" section.
+
+2019-09-20  Joel Brobecker  <brobecker@adacore.com>
+
 	GDB 8.3.1 released.
 
 2019-09-20  Ulrich Weigand  <uweigand@de.ibm.com>
diff --git a/gdb/NEWS b/gdb/NEWS
index 35b48d9..8f9b1d8 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -304,6 +304,20 @@ focus, winheight, +, -, >, <
 
 * Other MI changes
 
+ ** The default version of the MI interpreter is now 3 (-i=mi3).
+
+  ** The output of information about multi-location breakpoints (which is
+     syntactically incorrect in MI 2) has changed in MI 3.  This affects
+     the following commands and events:
+
+	- -break-insert
+	- -break-info
+	- =breakpoint-created
+	- =breakpoint-modified
+
+     The -fix-multi-location-breakpoint-output command can be used to enable
+     this behavior with previous MI versions.
+
  ** Backtraces and frames include a new optional field addr_flags which is
     given after the addr field.  On AArch64 this contains PAC if the address
     has been masked in the frame.  On all other targets the field is not
@@ -501,8 +515,6 @@ set style address intensity VALUE
 
 * MI changes
 
-  ** The default version of the MI interpreter is now 3 (-i=mi3).
-
   ** The '-data-disassemble' MI command now accepts an '-a' option to
      disassemble the whole function surrounding the given program
      counter value or function name.  Support for this feature can be
@@ -512,18 +524,6 @@ set style address intensity VALUE
   ** Command responses and notifications that include a frame now include
      the frame's architecture in a new "arch" attribute.
 
-  ** The output of information about multi-location breakpoints (which is
-     syntactically incorrect in MI 2) has changed in MI 3.  This affects
-     the following commands and events:
-
-	- -break-insert
-	- -break-info
-	- =breakpoint-created
-	- =breakpoint-modified
-
-     The -fix-multi-location-breakpoint-output command can be used to enable
-     this behavior with previous MI versions.
-
 * New native configurations
 
 GNU/Linux/RISC-V		riscv*-*-linux*


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-09-20 23:23 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-20 23:23 [binutils-gdb] gdb/NEWS: Move entries about MI v3 and multi-loc breakpoints after GDB 8.3 Joel Brobecker

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).