From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
macro@linux-mips.org, tom@tromey.com, simon.marchi@ericsson.com
Subject: GDB 8.1 release candidate on Friday (2018-01-12)
Date: Thu, 11 Jan 2018 03:59:00 -0000 [thread overview]
Message-ID: <20180111035934.x5nosnmrfp7r6cff@adacore.com> (raw)
Hello,
Thanks to Pedro, Tom, Maciej and Simon, I think we should be
in great shape.
The following are the issues that are still existing and should
be fixed before release:
* [Pedro] gdb/22583
gdb.base/breakpoint-in-ro-region.exp regressions on software
single-step tar gets
The following were recently fixed:
* [Maciej] remote/22597
Empty `qsThreadInfo' reply handling regression causing inability to execute
* [Pedro/Joel] gdb/22670
regressions in Ada caused by introduction of wild matching in
C++ patch series
* [SimonM] no PR
hurd: Add enough auxv support for AT_ENTRY for PIE binaries
The following has been analyzed as a testcase issue, rather than
a real issue -- hoping for the patch to be pushed soon:
* [TomT] no PR yet
Regression on 32-bit: gdb.guile/scm-ports.exp [Re: [RFA 1/2]
Fix two regress ions in scalar printing
https://sourceware.org/ml/gdb-patches/2017-12/msg00215.html
Tom proposed a patch. Pedro asked for some clarification,
Doug approved, and Tom provides some answers.
On my end, I am down to a very small number of failures when I use
AdaCore's testsuite. I still have to analyze them, but from where
I stand, only one may be related to the wild-matching series, but
I am guestimating that this is unlikely. Not blocking for the first
pre-release, IMO.
So, unless there are new issues we just discovered, I will proceed
with the first pre-release tomorrow!
--
Joel
next reply other threads:[~2018-01-11 3:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 3:59 Joel Brobecker [this message]
2018-01-11 9:57 ` Yao Qi
2018-01-12 19:27 ` Pedro Alves
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=20180111035934.x5nosnmrfp7r6cff@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.com \
--cc=tom@tromey.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).