From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, palves@redhat.com, sergiodj@redhat.com, yao.qi@arm.com
Subject: GDB 8.1 branching 2017-12-04 update
Date: Mon, 04 Dec 2017 14:56:00 -0000 [thread overview]
Message-ID: <20171204145644.hjd3jisybmndqn7p@adacore.com> (raw)
Hello,
As far as I know, the issues identified the last time we did
an update on the branch have all been either - defered to the next
release (ARMv8.3-A Pointer Authentication suppport), or pushed.
See: https://sourceware.org/gdb/wiki/GDB_8.1_Release
There are a number of PRs targetting 8.1 however. Should we wait
for those to be fixed before we branch?
* [TomT] PR breakpoint/22511
Regression in "commands"
* [PedroA] PR gdb/Bug 22499
8.0 regression: wrongly read $xmm0
Pedro sent a patch for review on Nov 29th, so I think we can wait
for that one before branching.
* [SergioDJ] PR cli/16224
add "pahole" functionality to ptype
Work is being done as we speak, with some patches sent.
I think we continue the wait.
In addition, we have the following unassigned PR:
* [YaoQ???] PR python/22475
Python API: breakpoint subclass: GDB crashes if function called through parse_and_eval() exits
Yao - are you working on this PR? I am asking because you marked it
as targetting 8.1 with the following message: "Set the target
milestone to 8.1, although it is not a regression from last release.".
I'll continue monitor those PRs closely, and hope that we can branch
by, say, early next week.
Am I missing other issues that you think should block the creation
of the 8.1 branch?
Thank you!
--
Joel
next reply other threads:[~2017-12-04 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 14:56 Joel Brobecker [this message]
2017-12-04 15:07 ` Tom Tromey
2017-12-04 15:21 ` Pedro Alves
2017-12-04 15:17 ` Pedro Alves
2017-12-04 17:02 ` Joel Brobecker
2017-12-09 0:17 ` Pedro Alves
2017-12-11 4:24 ` Joel Brobecker
2017-12-04 16:23 ` Yao Qi
2017-12-04 16:52 ` Joel Brobecker
2017-12-04 16:25 ` Pedro Alves
2017-12-04 17:11 ` Sergio Durigan Junior
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=20171204145644.hjd3jisybmndqn7p@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
--cc=tom@tromey.com \
--cc=yao.qi@arm.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).