From: Bob Rossi <bob@brasko.net>
To: gdb@sources.redhat.com
Subject: bob@brasko.net: Re: MI level command
Date: Fri, 09 Jul 2004 11:34:00 -0000 [thread overview]
Message-ID: <20040709113416.GA4979@white> (raw)
On Thu, Jul 08, 2004 at 07:33:17PM -0400, Alain Magloire wrote:
> Yellow
>
>
> Scenario: We want to know wich level of MI that we are currently working in.
> This can allow to adjust what MI command to use and how to parse them.
>
> Problems: No such command in MI and no GDB variable that we can test via -gdb-show.
> The version of gdb
> gdb --version
> show different things in different distributions, sometimes it is a number based on date
> etc ...
>
> So would a patch implementing
>
> -gdb-mi-level
> ^done,level=1
>
> be a good thing ?
I like this idea a lot. I will need it when I start getting more work
done on TGDB. However, there is another DRY problem. What functions act
which way for which level?
Basically, should every front end understand that
-file-list-exec-source-files outputs just the files for level 1 but it
also outputs the libraries the files belong to in level2?
One solution could be, for every MI function, we could generate a unique
key. For example, mi1-file-list-exec-source-files,
mi2-file-list-exec-source-files, ...
This key would tell the front end to use that particular parsing
function when checking the output of -file-list-exec-source-files.
Is this to wacky?
Thanks,
Bob Rossi
reply other threads:[~2004-07-09 11:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040709113416.GA4979@white \
--to=bob@brasko.net \
--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