From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Additional maintenance command for dumping target descriptions
Date: Tue, 16 Jun 2020 21:51:37 +0100 [thread overview]
Message-ID: <20200616205137.GU2737@embecosm.com> (raw)
In-Reply-To: <cover.1591871818.git.andrew.burgess@embecosm.com>
I messed up the in-reply-to header while posting a second iteration of
this patch series. The replacement patches ended up here:
https://sourceware.org/pipermail/gdb-patches/2020-June/169419.html
Thanks,
Andrew
* Andrew Burgess <andrew.burgess@embecosm.com> [2020-06-11 11:41:29 +0100]:
> After some fun and games debugging some target description issues I
> finally got fed up enough to implement something that I've wanted for
> a while. A mechanism to ask GDB what target description was sent from
> the target.
>
> Patch #1 was a quick hack to `maint print c-tdesc', which was easy,
> and did give me the information I needed, but the output format isn't
> great for what I wanted, so
>
> Patch #2 allows GDB developers to see in XML form the description that
> was sent from the target.
>
> Feedback welcome.
>
> Thanks,
> Andrew
>
>
> ---
>
> Andrew Burgess (2):
> gdb: Allow target description to be dumped even when it is remote
> gdb: New maintenance command to print XML target description
>
> gdb/ChangeLog | 17 +++
> gdb/NEWS | 6 +
> gdb/doc/ChangeLog | 5 +
> gdb/doc/gdb.texinfo | 9 ++
> gdb/target-descriptions.c | 102 +++++++++++++++-
> gdb/testsuite/ChangeLog | 6 +
> gdb/testsuite/gdb.xml/maint-xml-dump-01.xml | 10 ++
> gdb/testsuite/gdb.xml/maint-xml-dump-02.xml | 27 +++++
> gdb/testsuite/gdb.xml/maint-xml-dump.exp | 124 ++++++++++++++++++++
> gdbsupport/ChangeLog | 13 ++
> gdbsupport/tdesc.cc | 99 +++++++++++-----
> gdbsupport/tdesc.h | 15 +++
> 12 files changed, 399 insertions(+), 34 deletions(-)
> create mode 100644 gdb/testsuite/gdb.xml/maint-xml-dump-01.xml
> create mode 100644 gdb/testsuite/gdb.xml/maint-xml-dump-02.xml
> create mode 100644 gdb/testsuite/gdb.xml/maint-xml-dump.exp
>
> --
> 2.25.4
>
prev parent reply other threads:[~2020-06-16 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 10:41 Andrew Burgess
2020-06-11 10:41 ` [PATCH 1/2] gdb: Allow target description to be dumped even when it is remote Andrew Burgess
2020-06-11 11:33 ` Pedro Alves
2020-06-11 14:05 ` Andrew Burgess
2020-06-11 14:24 ` Pedro Alves
2020-06-11 10:41 ` [PATCH 2/2] gdb: New maintenance command to print XML target description Andrew Burgess
2020-06-11 13:10 ` Pedro Alves
2020-06-11 13:27 ` Eli Zaretskii
2020-06-11 19:50 ` [PATCH 0/2] Additional maintenance command for dumping target descriptions Christian Biesinger
2020-06-16 20:51 ` Andrew Burgess [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=20200616205137.GU2737@embecosm.com \
--to=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).