From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 8.2 branch WEDNESDAY? (2018-07-02 update)
Date: Mon, 02 Jul 2018 20:18:00 -0000 [thread overview]
Message-ID: <20180702201833.GA1080@adacore.com> (raw)
Hi everyone,
Fixed since the last update:
* (JoelB) SEGV on x86_64-windows due to fs_base/gs_base
Still in progress:
* (PhilippeW) Implement 'frame apply COMMAND', enhance 'thread apply COMMAND'
v3 sent on June 24th:
https://www.sourceware.org/ml/gdb-patches/2018-06/msg00559.html
At this point, it looks to me like there are still some questions
related to the new command-line interface itself, so it seems
better to give our the time to think this through. Let's keep
the pressure on, to get this patch series over the hump, but
let's also give ourselves the opportunity to observe the patch
in the master branch for a while before it makes it to a release.
Not blocking for the branch, but requested as nice to have:
* (AlanH) core file suport for aarch64 SVE
https://www.sourceware.org/ml/gdb-patches/2018-06/msg00580.html
ping: https://www.sourceware.org/ml/gdb-patches/2018-07/msg00015.html
The other two known issues are not blocking, IMO:
* (KevinB) gdb/23021 - Setting breakpoints with -freorder-blocks-and-partition
Not a regression, easy workaround.
https://sourceware.org/bugzilla/show_bug.cgi?id=23021
* (MaciejR) tdep/8282 - MIPS port needs `set disassembler-options'
Enhancement.
https://sourceware.org/bugzilla/show_bug.cgi?id=8282
All in all, I think we should go ahead and create the branch Wednesday.
We can still backport some patches if they are shown to have some benefit
while being reasonably safe or having a limited impact.
Thanks!
--
Joel
next reply other threads:[~2018-07-02 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 20:18 Joel Brobecker [this message]
2018-07-02 20:58 ` Philippe Waroquiers
2018-07-02 22:12 ` Joel Brobecker
2018-07-03 4:03 ` Philippe Waroquiers
2018-07-03 16:59 ` Pedro Alves
2018-07-02 23:06 ` Maciej W. Rozycki
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=20180702201833.GA1080@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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