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: Thu, 07 Oct 2004 22:42:00 -0000	[thread overview]
Message-ID: <20041007192830.GE14573@white> (raw)
In-Reply-To: <41659659.2030005@gnu.org>

On Thu, Oct 07, 2004 at 03:17:45PM -0400, Andrew Cagney wrote:
> >On Wed, Oct 06, 2004 at 06:36:02PM -0400, Andrew Cagney wrote:
> >
> >>>>>   * 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 )
> >>
> >>>
> >>>By "supported" you're expecting?  I've stated what people developing GDB 
> >>>test, and given you a pretty clear hint as to the consequence.
> >
> >
> >Understood, here is what I am hoping for at a minimum. 
> >
> >   * GDB supports at least 1 MI protocol for an official release. 
> >     Supporting multiple MI protocols would be better for me, but 
> >     not a requirement. If GDB could support multiple protocols it 
> >     would improve the chances of a given front end working with a
> >     given GDB.
> 
> But by "support" what do you mean - even a dictionary definition.  GDB 
> includes at least one MI implementation, but that says nothing about how 
> well it is either implemented or supported.

That's a good question.

Well, by support I simply mean, GDB is officially saying that a
particular MI protocol is implemented as it should be, that it is tested
to make sure that it works to the best of the GDB developers knowledge and 
that it is safe to use by front ends.

I am assuming that MI protocols in development ( right after a version
bump, but before a major release ) is considered unsupported. By this I
guess I mean that it should not be used by front ends until it is
stable. Maybe a better word for "support" in this context is "stable".

> >   * GDB supports at least 1 MI protocol for a CVS snapshot. The
> >     development MI protocol is probably not suitable for front ends
> >     to work with, until it has stabilized and become official. So I am
> >     hoping that GDB supports the last officially supported MI protocol
> >     during it's development process, until the development protocol is
> >     ready to become stable.
> >
> >
> >>>I was wondering more of what your project and its goals were.
> >
> >
> >CGDB is the front end I am working on, that said, I am actually not
> >doing all of the development of CGDB, just some of it.
> >
> >I am focusing more on libtgdb. This is basically a library that is
> >capable of communicating with GDB with any interface that GDB supports.
> 
> Why not instead help with libgdb, and the problem of being able to 
> directly link in the debugger?

What implementation approach is libgdb taking? Does it expect the front
end to link directly to it, so that a front end is tied to a particular
version of GDB?

I like the idea of a libgdb that is capable of communicating with any
version of GDB that talks a valid MI protocol. This makes the library
more flexible. I guess this is essentially the goal I am working towards
with libtgdb.

Bob Rossi


  reply	other threads:[~2004-10-07 19:28 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
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 [this message]
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=20041007192830.GE14573@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