This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
GDB 8.2.1 release -- 2018-11-06 status update
- From: Joel Brobecker <brobecker at adacore dot com>
- To: gdb-patches at sourceware dot org
- Date: Tue, 6 Nov 2018 14:21:09 -0800
- Subject: GDB 8.2.1 release -- 2018-11-06 status update
Hello everyone,
Hard to believe it, but it's been 2 months already since we released
8.2. So, time to think about the 8.2.1 release, if we want to target
Dec 5th as our release date.
So far, we have the following changes in 8.2.1:
* PR build/23516 (gdb build error under msys+mingw: strip can't handle gdb-add-index.exe)
* PR build/23623 (install-strip fails)
* PR rust/23626 (gdb crashes in upstream rust nil-enum test)
* PR rust/23650 (rust field name access error mentions "foo")
* PR python/23669 (gdb.execute("show commands") doesn't work)
We have the following PRs open with the target milestone set to 8.2.1:
* [*UNASSIGNED*] PR gdb/23663
gdb 8.1.1: undefined rpl_stat function with musl toolchains
https://sourceware.org/bugzilla/show_bug.cgi?id=23663
As far as I can tell, this one can be closed, now, thanks
to the following patch from Sergio:
- master: 3c025cfe5efc44eb4dfb03b53dca28e75096dd1e
- gdb-8.2-branch: 5de69bdbd0bbd7941b4cd93d4571f5e22cdb28be
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Move 'is_regular_file' from common-utils.c to filestuff.c
* [*UNASSIGNED*] PR gdb/23838
8.2 regression for invalid -data-directory
https://sourceware.org/bugzilla/show_bug.cgi?id=23838
Caused by [PATCH 01/40] Convert struct target_ops to C++] it seems.
It doesn't look very difficult to look into it; it just needs
a volunteer. Otherwise, it is likely that no progress will be
made towards a fix.
Note that there is a simple workaround, since the problem appears
limited to passing a file as a datadir, which is of course invalid.
So while not super elegant, I wouldn't consider this blocking
either.
Any other issues we should be considering? If yes, please let us know
here. I we agree that an issue is blocking for 8.2.1, then we'll need
a PR number describing the issue, and mark that PR with the 8.2.1 as
the target milestone.
Thank you!
--
Joel