From: Vladimir Prus <ghost@cs.msu.su>
To: Bob Rossi <bob@brasko.net>, gdb@sourceware.org
Subject: Re: GDB/MI async output token field
Date: Sun, 25 May 2014 07:16:00 -0000 [thread overview]
Message-ID: <538198B5.30208@cs.msu.su> (raw)
In-Reply-To: <20140523011405.GA10166@linux>
On 05/23/2014 05:14 AM, Bob Rossi wrote:
> Hi,
>
> I'm slowly working through the GDB/MI output command functionality.
>
> On this page,
> https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
>
> The documentation says,
> Note that for all async output, while the token is allowed by the
> grammar and may be output by future versions of gdb for select async
> output messages, it is generally omitted.
>
> Frontends should treat all async output as reporting general changes in
> the state of the target and there should be no need to associate async
> output to any prior command.
>
> I searched through the GDB source code and can't find a single place
> where this occurs.
>
> Does anyone know how to make a token appear in the async record?
> Did older versions do it?
>
> If GDB is not using this feature, I propose we remove this information
> from the manual until we actually need the functionality.
Bob,
such clarification will be good.
- Volodya
WARNING: multiple messages have this Message-ID
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sourceware.org
Subject: Re: GDB/MI async output token field
Date: Mon, 26 May 2014 00:14:00 -0000 [thread overview]
Message-ID: <538198B5.30208@cs.msu.su> (raw)
Message-ID: <20140526001400.X8YZk65fNPZk5zPvno0Iw0PE1ETz47TiDYN5ggOBIOA@z> (raw)
In-Reply-To: <20140523011405.GA10166@linux>
On 05/23/2014 05:14 AM, Bob Rossi wrote:
> Hi,
>
> I'm slowly working through the GDB/MI output command functionality.
>
> On this page,
> https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Output-Syntax.html#GDB_002fMI-Output-Syntax
>
> The documentation says,
> Note that for all async output, while the token is allowed by the
> grammar and may be output by future versions of gdb for select async
> output messages, it is generally omitted.
>
> Frontends should treat all async output as reporting general changes in
> the state of the target and there should be no need to associate async
> output to any prior command.
>
> I searched through the GDB source code and can't find a single place
> where this occurs.
>
> Does anyone know how to make a token appear in the async record?
> Did older versions do it?
>
> If GDB is not using this feature, I propose we remove this information
> from the manual until we actually need the functionality.
Bob,
such clarification will be good.
- Volodya
next prev parent reply other threads:[~2014-05-25 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 1:13 Bob Rossi
2014-05-25 7:16 ` Vladimir Prus [this message]
2014-05-26 0:14 ` Vladimir Prus
2014-05-28 7:59 ` Bob Rossi
2014-05-29 4:26 ` Bob Rossi
2014-05-29 17:04 ` Vladimir Prus
2014-05-29 19:22 ` Bob Rossi
2014-06-04 20:28 ` Vladimir Prus
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=538198B5.30208@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=bob@brasko.net \
--cc=gdb@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