public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] mi: print frame architecture when printing frames on an MI channel
Date: Tue, 21 Aug 2018 16:16:00 -0000	[thread overview]
Message-ID: <83k1ojd7bv.fsf@gnu.org> (raw)
In-Reply-To: <20180820204250.16301-1-jan.vrany@fit.cvut.cz> (message from Jan	Vrany on Mon, 20 Aug 2018 21:42:50 +0100)

> From: Jan Vrany <jan.vrany@fit.cvut.cz>
> Cc: Jan Vrany <jan.vrany@fit.cvut.cz>
> Date: Mon, 20 Aug 2018 21:42:50 +0100
> 
> 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.

Thanks.

> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -41,6 +41,11 @@ thread apply [all | COUNT | -COUNT] [FLAG]... COMMAND
>    FLAG arguments allow to control what output to produce and how to handle
>    errors raised when applying COMMAND to a thread.
>  
> +* MI changes
> +
> +  ** Command responses and notifications that include a frame now include
> +     the frame's architecture in a new "arch" attribute.
> +

This is OK.

> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index b931834400..635275d3ec 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -28001,7 +28001,7 @@ reason that execution stopped.
>  <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
>     frame=@{addr="0x08048564",func="main",
>     args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}],
> -   file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@}
> +   file="myprog.c",fullname="/home/nickrob/myprog.c",line="68",arch="i386:x86_64"@}

The modified line is now too long, please split it into two, otherwise
it might look badly in the printed version of the manual.

> @@ -28684,7 +28684,7 @@ for the watchpoint going out of scope.
>  wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@},
>  frame=@{func="callee4",args=[],
>  file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
> -fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
> +fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13",arch="i386:x86_64"@}

Likewise here, and everywhere else in the patch for the manual.

OK with those fixed.

      parent reply	other threads:[~2018-08-21 16:16 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
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             ` Eli Zaretskii [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=83k1ojd7bv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).