From: "Alain Magloire" <alain@qnx.com>
To: bob_rossi@cox.net (Bob Rossi)
Cc: gdb@sources.redhat.com
Subject: Re: gdb/mi or annotations detection
Date: Wed, 23 Apr 2003 14:51:00 -0000 [thread overview]
Message-ID: <200304231451.KAA31295@node1.ott.qnx.com> (raw)
In-Reply-To: <20030423111030.GA14799@white> from "Bob Rossi" at Apr 23, 2003 07:10:30 AM
>
> Hi,
>
> How is the front end supposed to detect whether or not it should use
> annotations or GDB/MI? I think there needs to be a way of doing this
> besides starting it once for detection/failure for MI, and then starting
> it again for annotations.
>
> Also, what about different versions of MI. As it progresses different
> versions will have different functionality. How will the front end know
> what functionality each version has?
>
I hear you loud and clear.
Eclipse/CDT, a debugger using heavily GDB/MI, is plague
with hacks trying to be compatible with all MI version.
This is probably not a problem with debuggers like insight, since they are
tied with a gdb version.
I thought, I had a PR on this, wait ... mi/1186
> ex.
> In the first release of MI there might not be the
> -symbol-info-linetable command. So, the front end will have to give
> commands 'info line' over and over. Then, when this command becomes
> available in the next release, the front end can start using it
> instead.
>
> The front end can not do a 'gdb --version' because usually there are
> gdb's installed that are cvs snapshots ( debian ).
>
"gdb --version", generates all sort of things depending on the platform, the distrubution, etc ..
not reliable
> Does anyone have any ideas?
>
-mi-level ? 8-)
bye,
next prev parent reply other threads:[~2003-04-23 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 11:10 Bob Rossi
2003-04-23 14:51 ` Alain Magloire [this message]
2003-04-25 2:36 ` Andrew Cagney
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=200304231451.KAA31295@node1.ott.qnx.com \
--to=alain@qnx.com \
--cc=bob_rossi@cox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).