From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: kevinb@redhat.com, sandra@codesourcery.com, tom@tromey.com,
ssbssa@yahoo.de, ro@cebitec.uni-bielefeld.de, ludo@gnu.org,
eliz@gnu.org, cbiesinger@google.com
Subject: GDB 10 branching - 2020-07-18 Update
Date: Sat, 18 Jul 2020 12:45:22 -0700 [thread overview]
Message-ID: <20200718194522.GA32708@adacore.com> (raw)
Hi everyone,
As you will see in the report below, a lot of been fixed since
the last update, but also we've also added a lot of new items.
To allow the process to converge, I propose we stop accepting
new items that aren't deemed blocking for the release.
For those who have items listed below, if you are blocked or
waiting for a review, please start pinging after the usual
waiting period (2 weeks after initial send, and weekly thereafter).
For those of us who have experience with the areas of the code
that the patches below are waiting on, and you have some time
to review them, that would be very helpful.
Thank you, everyone!
Fixed Since the Previous Update:
--------------------------------
Nice work guys!
* [AndrewB]
Fix Python unwinders and inline frames
https://sourceware.org/pipermail/gdb-patches/2020-June/169789.html
* [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
* [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
* [SebastianH (review by AndrewB]
sim/ppc: Fix linker error with GCC-10/-fno-common
https://sourceware.org/pipermail/gdb-patches/2020-July/170084.html
* [SandraL]
Skip directory tests in gdb.base/info_sources.exp on remote host
https://sourceware.org/pipermail/gdb-patches/2020-June/169894.html
* [SandraL]
Fix POSIX-isms in gdb.base/shell.exp
https://sourceware.org/pipermail/gdb-patches/2020-June/169865.html
https://sourceware.org/pipermail/gdb-patches/2020-July/170483.html
* [PaulC] <PR gdb/25716>
Modify Docs to avoid HTML filename collision on Windows
https://sourceware.org/bugzilla/show_bug.cgi?id=25716
https://sourceware.org/pipermail/gdb-patches/2020-June/169739.html
https://sourceware.org/pipermail/gdb-patches/2020-July/170232.html
Added Since the Last Update:
----------------------------
* [KevinB] <PR gdb/25631>
GDB cannot access unwritten-to mmap'd buffer from core file
https://sourceware.org/bugzilla/show_bug.cgi?id=25631
https://sourceware.org/pipermail/gdb-patches/2020-July/170158.html
Pedro sent minor comments on 2020-07-10, but is otherwise happy
with the patch series, so hopefully it gets pushed soon.
* [SandraL]
testsuite: gdb_wrapper handling polluting source directory with .o files
https://sourceware.org/pipermail/gdb-patches/2020-July/170224.html
Touches gdb.exp. No review so far. Not critical, IMO, but would
be nice to at least review the patch. This seems like a regression
compared to GDB 9.
Other Ongoing Items:
--------------------
* [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
Tom said he hasn't had time to look at Pedro's reply, unfortunately.
I'm not super confident that he'll have much time soon either.
Should we start looking at Plan B?
* [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 approved
that part of the patch. Waiting for a review on the GDB side (the part
in config/ is only used by GDB, so we will review it on the GDB side
as well).
* [LudovicC (reported by Simon)]
Add support for Guile 2.2
https://sourceware.org/pipermail/gdb-patches/2020-June/169936.html
Was reviewed by Simon, who conducted the best review he could
considering he doesn't know the area of the code well enough.
We've been waiting for a more experienced maintainer to comment,
with no success, so I suggested we go with Simon's review.
* [EliZ]
binutils: libctf build failure on Windows with mingw.org's MinGW
https://sourceware.org/pipermail/gdb-patches/2020-July/170042.html
2020-07-18: Joel just sent Nick a ping.
* [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
On going, but good progress since.
* [EliZ]
gdbserver: incorrect socklen_t configure test on mingw.org's MinGW
https://sourceware.org/pipermail/gdb-patches/2020-July/170019.html
Eli and Joel exchanged patches, but I don't see anything having
been officially submitted yet?
Not Critical, but Requested:
----------------------------
<none>
--
Joel
next reply other threads:[~2020-07-18 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 19:45 Joel Brobecker [this message]
2020-07-19 2:28 ` Eli Zaretskii
2020-07-19 15:03 ` Joel Brobecker
2020-07-25 7:56 ` Eli Zaretskii
2020-07-20 11:34 ` Rainer Orth
2020-07-20 15:22 ` Joel Brobecker
2020-07-21 20:38 ` Tom Tromey
2020-07-22 12:57 ` Joel Brobecker
2020-07-22 20:32 ` Kevin Buettner
2020-07-23 18:43 ` 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=20200718194522.GA32708@adacore.com \
--to=brobecker@adacore.com \
--cc=cbiesinger@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=ludo@gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=sandra@codesourcery.com \
--cc=ssbssa@yahoo.de \
--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