From: Pedro Alves <palves@redhat.com>
To: Jan Vrany <jan.vrany@fit.cvut.cz>, gdb-patches@sourceware.org
Subject: Re: [RFC] mi: print frame architecture when printing frames on an MI channel
Date: Wed, 22 Aug 2018 11:39:00 -0000 [thread overview]
Message-ID: <8772378f-c4a9-fd3b-0364-bf34fdbf4a8f@redhat.com> (raw)
In-Reply-To: <20180822094238.22304-1-jan.vrany@fit.cvut.cz>
Merged, thanks.
Pedro Alves
On 08/22/2018 10:42 AM, Jan Vrany wrote:
> When printing frames on an MI channel also print frame architecture
> like in:
>
> (gdb)
> -stack-list-frames 3 3
> ^done,stack=
> [frame={level="3",addr="0x000107a4",func="foo",
> file="recursive2.c",fullname="/home/foo/bar/recursive2.c",
> line="14",arch="i386:x86_64"}]
> (gdb)
>
> This is useful for MI clients that need to know the architecture in order
> to perform further analysis, for example to use their own disassembler to
> analyze machine code.
>
> gdb/Changelog:
>
> * stack.c (print_frame): Print frame architecture when printing on
> an MI output.
> * NEWS: Mention new "arch" attribute in frame output.
>
> gdb/testsuite/Changelog
>
> * lib/mi-support.exp (mi_expect_stop): Update regexp to
> accommodate new "arch" field in frame output.
> * gdb.mi/mi-return.exp: Likewise.
> * gdb.mi/mi-stack.exp: Likewise.
> * gdb.mi/mi-syn-frame.exp: Likewise.
> * gdb.mi/user-selected-context-sync.exp: Likewise.
>
> gdb/doc/Changelog
>
> * gdb.texinfo (The -stack-list-frames Command): Update description
> to mention "arch".
> Update MI examples thorough the document to contain "arch" in frame
> output.
next prev parent reply other threads:[~2018-08-22 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 5:57 [RFC] mi: Print " Jan Vrany
2018-08-10 10:30 ` Pedro Alves
2018-08-13 10:53 ` [RFC] mi: print " Jan Vrany
2018-08-16 19:01 ` Pedro Alves
2018-08-20 10:24 ` Jan Vrany
2018-08-20 11:16 ` Pedro Alves
2018-08-20 20:43 ` Jan Vrany
2018-08-21 15:42 ` Pedro Alves
2018-08-21 16:16 ` Eli Zaretskii
2018-08-22 9:43 ` Jan Vrany
2018-08-22 11:39 ` Pedro Alves [this message]
2018-08-24 20:22 ` Regression on gdb.arch/amd64-invalid-stack-*.exp (was: Re: [RFC] mi: print frame architecture when printing frames on an MI channel) Sergio Durigan Junior
2018-08-27 13:37 ` Jan Vrany
2018-08-21 16:16 ` [RFC] mi: print frame architecture when printing frames on an MI channel 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=8772378f-c4a9-fd3b-0364-bf34fdbf4a8f@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
/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