From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Sun, 22 Jun 2008 11:52:00 -0000 [thread overview]
Message-ID: <18526.15596.855756.886158@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080619190942.GA3744@adacore.com>
> | * Next GDB Release:
> |
> | Lots of new features, but not ready for real release. When
> | the features are in, need a little more maturing time before
> | shipping it in an official release. Suggest next release
> | in 6 months from now (Jan-Feb 2009).
> |
> | For people really interested in trying it out before the official
> | release, perhaps either:
> | - Announce various nightly tarballs that contain the features
> | - Or perhaps create a 6.9 branch but never release 6.9. Just
> | make various pre-releases 6.8.90, 6.8.91, etc.
If you are talking about branching now, I think that will mean that most
development will happen on the branch, i.e., there's not much point in
branching. You might as well make bugfix releases, or what GDB calls respins,
6.8.1, 6.8.2 etc from the 6.8 branch.
>...
> | * Fix and continue:
> |
> | Perhaps try to implement this feature through the use of Python.
> | For instance, use python to build a return value, and return that.
Apple GDB already has fix and continue. Couldn't that be used as a reference
implementaton?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-06-22 11:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 19:10 Joel Brobecker
2008-06-22 6:08 ` Thiago Jung Bauermann
2008-06-22 11:52 ` Nick Roberts [this message]
2008-06-22 13:53 ` Joel Brobecker
2008-06-23 15:17 ` Tom Tromey
2008-06-23 17:35 ` Jim Ingham
2008-06-23 21:55 ` Nick Roberts
2008-06-23 15:16 ` Tom Tromey
2008-06-26 0:24 ` Tom Tromey
2008-07-03 3:27 ` Thiago Jung Bauermann
2008-07-03 8:12 ` Andreas Schwab
2008-07-03 12:35 ` Daniel Jacobowitz
2008-07-03 14:28 ` Thiago Jung Bauermann
2008-07-04 2:33 ` Tom Tromey
2008-07-04 3:19 ` Daniel Jacobowitz
2008-06-23 21:46 ` Jason Molenda
2008-06-23 22:22 ` Nick Roberts
2008-06-24 21:18 ` Nick Roberts
2008-06-25 6:56 ` [MI] changing breakpoint location (Was: GDB Focus Group at the 2008 GCC Summit) Vladimir Prus
2008-06-23 22:09 ` GDB Focus Group at the 2008 GCC Summit Mark Kettenis
2008-06-23 22:26 ` Joel Brobecker
2008-06-24 8:35 ` Andrew STUBBS
2008-06-24 8:56 ` Andreas Schwab
2008-06-24 18:12 ` Michael Snyder
2008-06-24 18:28 ` Daniel Jacobowitz
2008-06-24 19:33 ` Dave Korn
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=18526.15596.855756.886158@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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