This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
GDB 8.0 release/branching update (10 more days to branching)
- From: Joel Brobecker <brobecker at adacore dot com>
- To: gdb-patches at sourceware dot org
- Cc: mishra dot nitish dot 88 at gmail dot com, Pedro Alves <palves at redhat dot com>, Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- Date: Sat, 4 Mar 2017 18:59:03 +0100
- Subject: GDB 8.0 release/branching update (10 more days to branching)
- Authentication-results: sourceware.org; auth=none
Hello everyone,
We are now about 10 days away from our tentative date for branching.
First of all, a big thank you for all of you who fixed some of those
PRs that were marked for 8.0!
As of now, we have 3 PRs currently open:
* gdb/21187 Static linking of libstdc++ and libgcc with GDB leads to
broken exception handling on AIX platform
I consider this one blocking for release (OK for branching):
New regression, no easy workaround.
The person who opened the PR actually sent a patch to
bugzilla, but I asked him (in Cc: here) to send the patch here,
so it can be reviewed, and possibly integrated. It's a
workaround, but it introduces a feature which could also
be useful in other contexts.
It should be sufficiently small and obvious that copyright
assignment not be an issue.
* gdb/21216 regression: TUI by: Eliminate make_cleanup_ui_file_delete
/ make ui_file a class hierarchy
We should be changing the subject to "missing carriage return
in TUI mode" or something like that. That's what it is about.
Clearly a regression, clearly blocking. But the hope is that
it be relatively simple to fix (from the look of it).
Already assigned.
* gdb/21169 GDBServer on ARM can crash the inferior while single stepping
Considered blocking, but only if it doesn't delay the release
unreasonably.
Antoine is this PR's champion.
So, all in all, at the moment, I don't think we have anything blocking
for creating the release. But if you know of some other issues, please
let us know.
At this point, we're getting sufficiently close to starting the release
process that I would like people to let me know when they mark
a PR for 8.0 (target milestone field), as this is the signal that
we can't release until it is fixed. And when you do, please explain
what your reasons are.
Thank you!
--
Joel