From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: Re: MI documentation
Date: Thu, 30 Sep 2004 06:36:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20040930082856.01cf3990@NT_SERVER> (raw)
In-Reply-To: <20040929173133.GB1054@white>
>I was wondering how GDB documents the different versions of MI. For
>instance, how do you know what MI commands are available with
>specific versions of MI? What fields do the commands output for
>specific versions? What asynchronous notifications are possibly outputted
>with MI version 1,2,3?
I think the way to go is the probing of each needed command. If it's
available the frontend can use it, if not the frontend needs a fallback.
This is done e.g. in the remote protocol. If the vCont command is not
implemented the simpler s and c commands are used. This is somehow
similar to the MI. If the tagged commands are not implemented (older
gdb) the untagged commands can be used, even with less reliability.
So THE ONE version number is not really usefull as you also stated
earlier. But I don't know how a frontend can _ask_ what async
notifications could come.
bye Fabi
next prev parent reply other threads:[~2004-09-30 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 17:31 Bob Rossi
2004-09-30 6:36 ` Fabian Cenedese [this message]
2004-09-30 11:49 ` Bob Rossi
2004-09-30 14:01 ` Eli Zaretskii
2004-09-30 20:55 ` Bob Rossi
2004-09-30 13:55 ` 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=5.2.0.9.1.20040930082856.01cf3990@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@sources.redhat.com \
/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