Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Arnaud Charlet <charlet@ACT-Europe.FR>, gdb@sources.redhat.com
Subject: Re: [Various] obsoleting the annotate level 2 interface
Date: Wed, 29 Jan 2003 16:34:00 -0000	[thread overview]
Message-ID: <20030129173411.A14044@dublin.int.act-europe.fr> (raw)
In-Reply-To: <3E37FEF4.7080904@redhat.com>; from ac131313@redhat.com on Wed, Jan 29, 2003 at 11:19:00AM -0500

> Um, by stable you mean?  Each iteration of GDB leads to changes in both 
> the MI and the CLI.  However, at at least with the MI those changes are 
> identified, documented and tested.

By stable I mean that the set of commands and their output are reasonably
stable and do not change significantly from one version to another.

> People have been working on that.  Apple has a hacked GDB where it works 
> NOW!

Right, that's not acceptable in the context of a multipurpose and portable
GUI front-end, where basically people can plug the version of gdb they like.
So Apple's approach of hacking a particular version of gdb is not feasible,
and not something that can be maintained in the long run.

> The problems they have encountered have been turned into bug reports. 
> See the bug database.  The only big one is the console and both Apple 
> and Eclipse managed to hack around it.

Does it mean that there are no plans to actually fix this critical missing
feature, and that each front-end will have to "hack around it" ?

I will look again at Eclipse support for gdb. Last time I looked, its
support was relatively simple, certainly not at the same level than what
GVD offers.

Arno


  reply	other threads:[~2003-01-29 16:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 20:05 Jim Blandy
2003-01-28 20:36 ` Andrew Cagney
2003-01-29  6:14   ` Eli Zaretskii
2003-01-29 21:56     ` Jim Blandy
2003-01-28 22:29 ` Arnaud Charlet
2003-01-29  5:38   ` Andrew Cagney
2003-01-29  8:55     ` Arnaud Charlet
2003-01-29 15:19       ` Andrew Cagney
2003-01-29 15:31         ` Arnaud Charlet
2003-01-29 15:43           ` Andrew Cagney
2003-01-29 15:51             ` Arnaud Charlet
2003-01-29 15:55               ` Christopher Faylor
2003-01-29 16:01                 ` Arnaud Charlet
2003-01-29 16:19                   ` Andrew Cagney
2003-01-29 16:34                     ` Arnaud Charlet [this message]
2003-01-29 17:16                       ` Andrew Cagney
2003-01-29 19:03                       ` Tom Tromey
2003-01-29 22:38                         ` Jim Blandy
2003-01-29 17:19         ` Eli Zaretskii
2003-01-31 20:14 Nick Roberts
2003-01-31 20:56 ` Elena Zannoni
2003-01-31 21:10   ` Andrew Cagney
     [not found]     ` <15931.6572.456534.588251@nick.uklinux.net>
     [not found]       ` <15931.8581.923838.921739@localhost.redhat.com>
2003-02-01 16:16         ` Nick Roberts
2003-01-31 22:33   ` Nick Roberts
2003-02-01  4:13   ` Jim Blandy
     [not found] <1044050405.3227.ezmlm@sources.redhat.com>
2003-02-01  0:43 ` Jim Ingham

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=20030129173411.A14044@dublin.int.act-europe.fr \
    --to=charlet@act-europe.fr \
    --cc=ac131313@redhat.com \
    --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