From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch NEWS+7.6] List the MI "fullname" change
Date: Wed, 03 Apr 2013 18:22:00 -0000 [thread overview]
Message-ID: <20130403175027.GA5688@host2.jankratochvil.net> (raw)
Hi Eli,
the was change
[rfc] Print MI fullname even for non-existing files
http://sourceware.org/ml/gdb-patches/2012-12/msg00557.html
Message-ID: <20121217155859.GA8029@host2.jankratochvil.net>
which Pedro has found
http://sourceware.org/ml/gdb-patches/2013-04/msg00040.html
is not reflected in gdb/NEWS.
Thanks,
Jan
gdb/
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.
diff --git a/gdb/NEWS b/gdb/NEWS
index a2a7320..621da2c 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -220,8 +220,7 @@ show debug notification
** 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
@@ -232,6 +231,8 @@ show debug notification
** 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 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
next reply other threads:[~2013-04-03 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 18:22 Jan Kratochvil [this message]
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 ` [commit+7.6] " Jan Kratochvil
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=20130403175027.GA5688@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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