From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: [commit+7.6] [patch NEWS+7.6] List the MI "fullname" change
Date: Wed, 03 Apr 2013 19:48:00 -0000 [thread overview]
Message-ID: <20130403183055.GA8950@host2.jankratochvil.net> (raw)
In-Reply-To: <83k3ojh3tx.fsf@gnu.org>
On Wed, 03 Apr 2013 20:22:18 +0200, Eli Zaretskii wrote:
> I didn't mean to drop "the", so '...present along with the "file"
> field...'.
>
> Sorry for being unclear.
Checked in:
http://sourceware.org/ml/gdb-cvs/2013-04/msg00034.html
and for 7.6:
http://sourceware.org/ml/gdb-cvs/2013-04/msg00035.html
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2013-04/msg00034.html
--- src/gdb/ChangeLog 2013/04/03 18:04:33 1.15362
+++ src/gdb/ChangeLog 2013/04/03 18:28:49 1.15363
@@ -1,3 +1,8 @@
+2013-04-03 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * NEWS (Changes in GDB 7.6): Update the data-disassemble for "fullname".
+ New entry about "fullname" presence.
+
2013-04-03 Pedro Alves <palves@redhat.com>
* NEWS: Mention x86_64/Cygwin as new native configuration.
--- src/gdb/NEWS 2013/04/03 18:04:33 1.582
+++ src/gdb/NEWS 2013/04/03 18:28:49 1.583
@@ -221,8 +221,7 @@
** Memory changes are now notified using new async record
"=memory-changed".
** The data-disassemble command response will include a "fullname" field
- containing the absolute file name when GDB can determine it and source
- has been requested.
+ containing the absolute file name when source has been requested.
** New optional parameter COUNT added to the "-data-write-memory-bytes"
command, to allow pattern filling of memory areas.
** New commands "-catch-load"/"-catch-unload" added for intercepting
@@ -233,6 +232,8 @@
** Output of the "-trace-status" command includes a "trace-file" field
containing the name of the trace file being examined. This field is
optional, and only present when examining a trace file.
+ ** The "fullname" field is now always present along with the "file" field,
+ even if the file cannot be found by GDB.
* GDB now supports the "mini debuginfo" section, .gnu_debugdata.
You must have the LZMA library available when configuring GDB for this
prev parent reply other threads:[~2013-04-03 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 18:22 Jan Kratochvil
2013-04-03 18:58 ` Eli Zaretskii
2013-04-03 19:33 ` Jan Kratochvil
2013-04-03 19:34 ` Eli Zaretskii
2013-04-03 19:48 ` Jan Kratochvil [this message]
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=20130403183055.GA8950@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.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