From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Luis Machado <luis.machado@linaro.org>,
Andrew Burgess <andrew.burgess@embecosm.com>,
Tom Tromey <tom@tromey.com>, Hannes Domani <ssbssa@yahoo.de>
Subject: GDB 10 branching - 2020-06-27 Update
Date: Sat, 27 Jun 2020 08:40:05 -0700 [thread overview]
Message-ID: <20200627154005.GA5618@adacore.com> (raw)
Hi everyone,
Great progress last week, as the first section of this report will
indicate! So far, we're down to 3 identified issues we would like
to fix before branching. As always, if you see anything else that
you think should make the list, please let us know!
As a reminder, the proposal was to try to branch during the weekend
of July 4th if we can, which is very soon. From there, we would then
aim for a release 2-3 weeks later.
Fixed Since the Previous Update:
--------------------------------
* [RainerO/PedroA]
<PR gdb/25939> [10 regression] run fails with ICE on Solaris
https://sourceware.org/bugzilla/show_bug.cgi?id=25939
* [AndrewB/TomT]
QEMU / GDB compatibility on RISCV64 ELF (failure to fetch some registers)
https://sourceware.org/pipermail/gdb-patches/2020-June/169393.html
Reference to the patch series that got pushed a couple of days ago:
https://sourceware.org/pipermail/gdb-patches/2020-June/169561.html
Subject: RISC-V target description and register handling fixes
* [PhilippeW]
<PR gdb/25475>
https://sourceware.org/bugzilla/show_bug.cgi?id=25475
* [PhilippeW]
Allow the user to define default args for aliases
https://sourceware.org/pipermail/gdb-patches/2020-June/169467.html
Added Since the Last Update:
----------------------------
* [Unassigned (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
Patch causes some options to be missing when compiling test code.
* [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). Andrew provided in his commit revlog
a very detailed explanation of the situation.
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
Not Critical, but Requested:
----------------------------
<none>
--
Joel
next reply other threads:[~2020-06-27 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 15:40 Joel Brobecker [this message]
2020-07-01 21:11 ` Rainer Orth
2020-07-01 21:21 ` Joel Brobecker
2020-07-02 21:49 ` Simon Marchi
2020-07-03 15:10 ` Joel Brobecker
2020-07-03 15:12 ` Simon Marchi
2020-07-10 23:07 ` Pedro Alves
2020-07-03 0:35 ` Simon Marchi
2020-07-03 7:30 ` Eli Zaretskii
2020-07-03 15:06 ` Joel Brobecker
2020-07-03 15:15 ` Simon Marchi
2020-07-03 8:15 ` Sebastian Huber
2020-07-03 13:07 ` Andrew Burgess
2020-07-03 15:07 ` 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=20200627154005.GA5618@adacore.com \
--to=brobecker@adacore.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--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