Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: gdb@sourceware.cygnus.com
Subject: Next release of GDB
Date: Thu, 02 Sep 1999 18:20:00 -0000	[thread overview]
Message-ID: <199909030120.SAA20919@andros.cygnus.com> (raw)

I'd like us to start planning for the next release of GDB.  This might
seem a bit soon after 4.18, but I think a year's interval is too long,
what with all the changes that are going on, and historically the
release tends to take a couple months longer than originally
anticipated anyway.  The following plan is just my idea, feel free to
comment on big and little issues...

Here are the things that I think must be in the next release:

* Complete GNU/Linux support, all distros/versions
* Complete *BSD support
* Support for current (2.95.x) GCC/G++

In addition, there should be no submitted patch backlog - all patches
must be accepted and incorporated, or else rejected.

Here are some additional things that I would like to see, but that
ought not to hold up the release if they can't be gotten in:

* first version of libgdb, w/Guile scripting
* GNU/Linux thread_db library support
* asynchronous execution for GNU/Linux
* fork following for GNU/Linux
* HP WDB 1.1 bits
* Apple MacOS X support bits
* Current VxWorks (Tornado) support bits
* Current LynxOS support bits
* m68k BDM patches
* Ada language support

There are probably many other important things that I'm forgetting,
please speak up and remind me about them!

Since the next release of GDB will have changed more since the last
release than any since 1991, I think it should be called 5.0.  This
will also give us a new baseline for a new generation of improvements,
which is why I'm especially keen to get old divergences reduced before
we set off on the next round of changes.

Timewise, we should try to be done with major patch incorporation by
the end of November, do testing in December, and have something on
ftp sites by 12/31, just in time to help solve Y2K bugs...

"GDB 5.0: The Debugger for the Next Millenium"

								Stan
From brendan@dgs.monash.edu.au Thu Sep 02 19:25:00 1999
From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Stan Shebs <shebs@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Next release of GDB
Date: Thu, 02 Sep 1999 19:25:00 -0000
Message-id: <37CF319F.8FAA5579@dgs.monash.edu.au>
References: <199909030120.SAA20919@andros.cygnus.com>
X-SW-Source: 1999-q3/msg00284.html
Content-length: 685

Stan Shebs wrote:

> Here are some additional things that I would like to see, but that
> ought not to hold up the release if they can't be gotten in:
>
> * first version of libgdb, w/Guile scripting
> * GNU/Linux thread_db library support
> * asynchronous execution for GNU/Linux
> * fork following for GNU/Linux
> * HP WDB 1.1 bits
> * Apple MacOS X support bits
> * Current VxWorks (Tornado) support bits
> * Current LynxOS support bits
> * m68k BDM patches
> * Ada language support

All BDM patches please !!
I know Scott Howard has quite a few changes for the PowerPC BDMs.
The "ocd reg" command comes to mind.


> "GDB 5.0: The Debugger for the Next Millenium"

Cool.

Brendan.


             reply	other threads:[~1999-09-02 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-02 18:20 Stan Shebs [this message]
1999-09-08 12:54 ` J. Kean Johnston

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=199909030120.SAA20919@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb@sourceware.cygnus.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