From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: RFA: patch NEWS for MI changes (Was: [0/3] RFC: fix PR mi/8444)
Date: Mon, 05 Dec 2011 21:52:00 -0000 [thread overview]
Message-ID: <m3wraaofg1.fsf_-_@fleche.redhat.com> (raw)
In-Reply-To: <201112041459.05327.pedro@codesourcery.com> (Pedro Alves's message of "Sun, 4 Dec 2011 14:59:05 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> I think this should have a NEWS entry. MI changes should
Pedro> be advertised so frontend maintainers notice them.
I agree.
I went through ChangeLog and looked at the various MI changes from this
year. This is what I came up with.
Ok?
Tom
2011-12-05 Tom Tromey <tromey@redhat.com>
* NEWS: Add MI news.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.470
diff -u -r1.470 NEWS
--- NEWS 29 Nov 2011 03:49:09 -0000 1.470
+++ NEWS 5 Dec 2011 21:50:49 -0000
@@ -65,6 +65,16 @@
the standard Python "iteritems" method, it will recursively traverse
any anonymous fields.
+* MI changes
+
+ ** "*stopped" events can report several new "reason"s, such as
+ "solib-event".
+
+ ** Breakpoint changes are now notified using new async records, like
+ "=breakpoint-modified".
+
+ ** New command -ada-task-info.
+
* libthread-db-search-path now supports two special values: $sdir and $pdir.
$sdir specifies the default system locations of shared libraries.
$pdir specifies the directory where the libpthread used by the application
next prev parent reply other threads:[~2011-12-05 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 19:58 [0/3] RFC: fix PR mi/8444 Tom Tromey
2011-12-04 14:59 ` Pedro Alves
2011-12-05 21:52 ` Tom Tromey [this message]
2011-12-06 5:47 ` RFA: patch NEWS for MI changes (Was: [0/3] RFC: fix PR mi/8444) 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=m3wraaofg1.fsf_-_@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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