Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release: Start of stabilization period ?
Date: Sun, 13 Oct 2019 14:35:00 -0000	[thread overview]
Message-ID: <d2597c391501c2fccc168251a7c6be5b91cf66c6.camel@skynet.be> (raw)
In-Reply-To: <20191012191938.GA2675@adacore.com>

On Sat, 2019-10-12 at 15:19 -0400, Joel Brobecker wrote:
> Hi everyone,
> 
> Now that the 8.3.1 release is out, I think now is a good time to
> prepare the 9.1 release. I looked at the gdb/NEWS file and it is
> chockablock full of goodies!
> 
> At the moment, there aren't any issues in bugzilla that are marked
> pending for GDB 9.1.
> 
> Are there any issues that people would like to be fixed, before
> we release GDB 9.1? For those issues, it would be good to see whether
> these are blocking issues prior to branching, or not.
> 
> In the meantime, while we start collecting the list of issues
> we want to fix for 9.1, if there aren't any objection, I'd like us
> to start a cooling period so as to stabilize GDB prior to branching.

Here are the patches sent for review
(by order of first submission, but pointing at the last exchange):

RFC Have an option to tell GDB to detect and possibly handle mismatched exec-files
https://sourceware.org/ml/gdb-patches/2019-09/msg00580.html

Convenience functions $_gdb_setting/$_gdb_setting_str
https://sourceware.org/ml/gdb-patches/2019-09/msg00581.html

Allow the user to define default leading args for commands and aliases
https://sourceware.org/ml/gdb-patches/2019-09/msg00583.html

Implement 'print -raw-values' and 'set print raw-values on|off'
https://sourceware.org/ml/gdb-patches/2019-09/msg00582.html

More flexible user-defined commands prefixing and naming.
https://sourceware.org/ml/gdb-patches/2019-09/msg00588.html


And here is the advocacy to include them ...

The first one fixes an annoying GDB behavior.

I think the second one is now ready to push.

The third and fourth are useful additions or complements
to the GDB 9.1 'with' and 'option framework' functionalities.

Assuming that with the stabilisation period, there is more review
bandwidth, then the last one is nice to have :).

Thanks
Philippe



  parent reply	other threads:[~2019-10-13 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 19:19 Joel Brobecker
2019-10-13  1:19 ` Christian Biesinger via gdb-patches
2019-10-13 13:58   ` Tom de Vries
2019-10-15 15:20     ` Joel Brobecker
2019-10-15 15:23       ` Tom de Vries
2019-10-15 15:37         ` Joel Brobecker
2019-10-15 15:16   ` Joel Brobecker
2019-10-13 14:35 ` Philippe Waroquiers [this message]
2019-10-15 15:37   ` Joel Brobecker
2019-10-14 17:44 ` Tom Tromey
2019-10-15 15:53   ` Joel Brobecker

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=d2597c391501c2fccc168251a7c6be5b91cf66c6.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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