From: Joel Brobecker <brobecker@adacore.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release -- 2019-11-01 Update
Date: Mon, 11 Nov 2019 17:44:00 -0000 [thread overview]
Message-ID: <20191111174450.GB23568@adacore.com> (raw)
In-Reply-To: <c08df5826a275a66e9fd130516b2e9efd8f713bc.camel@skynet.be>
Hi Philippe,
> If there is some more review bandwidth before 9.1, here are the list
> of remaining pending patches:
>
>
> 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
>
> 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
I've added those to the list I'll track as, unlike some other patches
that others highlighted, these don't seem overly risky for landing
just before branching, or being backported.
--
Joel
next prev parent reply other threads:[~2019-11-11 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:16 Joel Brobecker
2019-11-04 21:02 ` Philippe Waroquiers
2019-11-11 17:44 ` Joel Brobecker [this message]
2019-11-04 21:26 ` Jonah Graham
2019-11-11 16:05 ` Joel Brobecker
2019-11-05 0:14 ` Christian Biesinger via gdb-patches
2019-11-11 17:48 ` Joel Brobecker
2019-11-15 1:21 ` Christian Biesinger via gdb-patches
2019-11-15 2:17 ` Joel Brobecker
2019-11-19 3:02 ` Christian Biesinger via gdb-patches
2019-11-05 20:54 ` Tom Tromey
2019-11-05 21:33 ` Simon Marchi
2019-11-10 22:40 ` Andrew Burgess
2019-11-11 17:50 ` 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=20191111174450.GB23568@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
/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