Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Bob's MI objective
Date: Wed, 06 Oct 2004 22:36:00 -0000	[thread overview]
Message-ID: <20041006212652.GB13271@white> (raw)
In-Reply-To: <416451B0.3060306@gnu.org>

On Wed, Oct 06, 2004 at 04:12:32PM -0400, Andrew Cagney wrote:
> Bob, what's your overall objective here?  Perhaphs our lack of 
> appreciation of your overriding goals is the reason that some (at least 
> I) are feeling somewhat puzzled and confused.

I want an MI version named after myself, specifically 'gdb -i=bobmi'
No seriously,

I already have a front end that works off of GDB's annotate two feature.
I understand that the annotate two interface could be removed from GDB. 
I asked you a year or two ago to wait until MI is capable of replacing the
annotations. I personally wrote the two commands to MI
-file-list-exec-source-file
-file-list-exec-source-files
that make MI capable of replacing the annotations interface for front
ends that do not already know what files are involved in the users
applications. I appreciate your patience in this matter. I feel that I
have done my part in this matter to prove to you that I am interested
and involved with the MI interface evolving for small front ends. 

Now I am beginning to add the MI interface to my front end. I spent the
last few weeks looking at the grammar of the currently documented MI
output syntax. The documentation is incorrect, but mostly correct and I 
suggested some changes to it so that others could benefit.
I have come up with the rules and generated a parser that is capable of
parsing an MI output command. I would like to validate the output of
GDB's MI commands in the testsuite to prove to us all that every MI command 
obeys the protocol. This is something I am interested in doing for the 
benefit of all front end developers. Not just myself.

Now, my next objective is to figure these things,

   * I would like to know what GDB's policy is in regards to supporting old
     MI protocols.  ( I have received several opposing views on this )

   * I would like to ensure that my front end works well with snapshots
     of GDB. I do not want to work with the MI development protocol, I
     just want to work with the last officially supported protocol.

   * I would like to make sure that development protocols are never used
     by my front end and that I can figure out all of the officially 
     supported MI protocols that a given GDB supports.

By being able to understand the highest officially supported protocol
that both GDB and my front end understand is critical to me. I think it is 
safe to say that a front end needs to know the MI protocols that a given 
GDB supports. The way we get that info from GDB to the front end is the 
question in debate.

Thanks,
Bob Rossi


  reply	other threads:[~2004-10-06 21:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 20:13 Andrew Cagney
2004-10-06 22:36 ` Bob Rossi [this message]
2004-10-07  2:40   ` Andrew Cagney
2004-10-07 17:20     ` Bob Rossi
2004-10-07 20:50       ` Andrew Cagney
2004-10-07 22:42         ` Bob Rossi
2004-10-08  8:40           ` Fabian Cenedese
2004-10-08 13:17             ` Bob Rossi
2004-10-08  7:17   ` Bob Rossi
2004-10-08 12:41     ` Eli Zaretskii
2004-10-08 13:23       ` Bob Rossi
2004-10-08 13:42         ` Eli Zaretskii
2004-10-08 16:34         ` Daniel Jacobowitz
2004-10-08 16:28       ` Daniel Jacobowitz
2004-10-08 18:57         ` Eli Zaretskii
2004-10-09 11:14           ` Andrew Cagney
2004-10-10  4:06             ` Bob Rossi
2004-10-11  2:00               ` Bob Rossi
2004-10-11 14:12                 ` Andrew Cagney
2004-10-11 17:22                   ` Bob Rossi
2004-10-12 22:15                     ` Michael Chastain

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=20041006212652.GB13271@white \
    --to=bob@brasko.net \
    --cc=cagney@gnu.org \
    --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