From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Pedro Alves <palves@redhat.com>, Simon Marchi <simark@simark.ca>,
Sebastian Huber <sebastian.huber@embedded-brains.de>,
Eli Zaretskii <eliz@gnu.org>,
Christian Biesinger <cbiesinger@google.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Tom Tromey <tromey@adacore.com>, Hannes Domani <ssbssa@yahoo.de>
Subject: GDB 10 branching - 2020-07-03 Update
Date: Fri, 3 Jul 2020 10:57:10 -0700 [thread overview]
Message-ID: <20200703175710.GA10485@adacore.com> (raw)
Hi everyone,
Here is a the current status in terms of the GDB 10 release branching.
As you can see, we had a significant number of new items added since
last time.
As always, let us know if you have comments on those, or if there are
other issues you think we should be aware of.
Thank you!
Fixed Since the Previous Update:
--------------------------------
* [TomDV (reported by LuisM)] <PR gdb/26175>
Regression on testsuite due to changes to default_target_compile
https://sourceware.org/bugzilla/show_bug.cgi?id=26175
Added Since the Last Update:
----------------------------
* [RainerO]
Unify Solaris procfs and largefile handling
https://sourceware.org/pipermail/gdb-patches/2020-June/169977.html
Seems to require a fair amount of coordination. binutils seems
on board; what about GCC (for the part in config/)?
* [Pedro/Simon (reported by SimonM)] <PR gdb/26199>
GDB goes in busy loop when interrupting non-stop program
https://sourceware.org/bugzilla/show_bug.cgi?id=26199
* [??? (reported by Simon)]
Add support for Guile 2.2
https://sourceware.org/pipermail/gdb-patches/2020-June/169936.html
Looking for a GDB Maintainer feeling competent enough to review
the patch. If not, I suggest we go with Simon's approach of
a basic review for the generic requirements and check for obvious
red flags.
* [SebastianH (review by AndrewB] <PR sim/26194>
sim/igen: Fix linker error with GCC-10/-fno-common
https://sourceware.org/pipermail/gdb-patches/2020-July/170083.html
Approved, so push should be imminent.
* [SebastianH (review by AndrewB]
sim/ppc: Fix linker error with GCC-10/-fno-common
https://sourceware.org/pipermail/gdb-patches/2020-July/170084.html
Approved, so push should be imminent.
* [EliZ]
binutils: libctf build failure on Windows with mingw.org's MinGW
https://sourceware.org/pipermail/gdb-patches/2020-July/170042.html
* [ChristianB (reported by Eli)]
Update gnulib to include fixes needed for mingw.org's MinGW
https://sourceware.org/pipermail/gdb-patches/2020-June/169987.html
https://sourceware.org/pipermail/gdb-patches/2020-July/170059.html
* [EliZ]
gdbserver: incorrect socklen_t configure test on mingw.org's MinGW
https://sourceware.org/pipermail/gdb-patches/2020-July/170019.html
Other Ongoing Items:
--------------------
* [AndrewB]
Fix Python unwinders and inline frames
https://sourceware.org/pipermail/gdb-patches/2020-June/169789.html
Difficult issue to solve. Andrew mentioned he would appreciate
feedback from others who might be familiar with this area
(inline frames hanlding), and just sent another ping about it,
warning that it would be pushed in a next couple of days if
no comments. Andrew provided in his commit revlog a very detailed
explanation of the situation.
* [TomT/HannesD] <PR win32/25302>
Mismatching fstat() function calls in gdb_bfd_open() and cache_bstat()
https://sourceware.org/bugzilla/show_bug.cgi?id=25302
Latest discussion at:
https://sourceware.org/pipermail/gdb-patches/2020-June/169670.html
Not Critical, but Requested:
----------------------------
<none>
--
Joel
next reply other threads:[~2020-07-03 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 17:57 Joel Brobecker [this message]
2020-07-03 18:15 ` Rainer Orth
2020-07-06 21:18 ` Sandra Loosemore
2020-07-07 0:44 ` Sandra Loosemore
2020-07-07 22:54 ` Kevin Buettner
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=20200703175710.GA10485@adacore.com \
--to=brobecker@adacore.com \
--cc=andrew.burgess@embecosm.com \
--cc=cbiesinger@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=sebastian.huber@embedded-brains.de \
--cc=simark@simark.ca \
--cc=ssbssa@yahoo.de \
--cc=tromey@adacore.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