From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: mishra.nitish.88@gmail.com,
Tremblay <antoine.tremblay@ericsson.com>,
keiths@redhat.com, "Wiederhake, Tim" <tim.wiederhake@intel.com>
Subject: GDB 8.0 release/branching 2017-03-20 update
Date: Mon, 20 Mar 2017 20:16:00 -0000 [thread overview]
Message-ID: <20170320201629.pbjzaqsnvs7dx7f2@adacore.com> (raw)
Hello everyone,
We are now roughly at our target branching date. Looking at the list
of PRs marked for 8.0, we still have:
* gdb/21187 Static linking of libstdc++ and libgcc with GDB leads to
broken exception handling on AIX platform
I think Nitish is having a little difficulties with
the submission process, but the patch is looking cleaner.
Hopefully it'll be accepted soon.
* gdb/21169 GDBServer on ARM can crash the inferior while single stepping
Any update on this one? The previous status was:
| Considered blocking, but only if it doesn't delay the release
| unreasonably.
|
| Antoine is this PR's champion.
* gdb/14441 Need to support DW_TAG_rvalue_reference_type
I think the part that we need for 8.0 is on the verge of
getting in. Keith is on top of it, as far as I can remember.
Keith?
In the "maybe" section, we have:
* [TimWiederhake] new "record" Python API should be finalized before we release
(otherwise, we might be have a compatibility issue if we don't design
them well from the start)
https://sourceware.org/ml/gdb-patches/2017-03/msg00023.html
Looks like the discussion is still fairly active, and I am starting
to think that we might be putting too much pressure to get this done
before 8.0.
What's the status of this API? Is this something entirely new?
Or something that replaces an API which was already contributed?
If it's a replacement, was the older API part of a previous release?
Looking at the NEWS file, it looks like it's something which
would be new. So we could decide to not rush this into 8.0,
and wait for 8.1, when we're more certain of the API we'd like.
It would also give it another 6 months of use where we can
easily change the API, before it's part of a release, and therefore
harder to change.
* [TimWiederhake] Build issue when using Python 2.6.x
What's the status of that patch? My questions were answered,
but was the patch reviewed?
https://www.sourceware.org/ml/gdb-patches/2017-03/msg00053.html
Thanks!
--
Joel
next reply other threads:[~2017-03-20 20:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:16 Joel Brobecker [this message]
2017-03-20 20:21 ` Keith Seitz
2017-03-20 22:39 ` Yao Qi
2017-03-20 22:47 ` Yao Qi
2017-03-20 22:52 ` Joel Brobecker
2017-03-20 23:03 ` Yao Qi
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 7:35 ` Wiederhake, Tim
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 13:07 ` Yao Qi
2017-03-21 13:31 ` Joel Brobecker
2017-03-22 13:58 ` Metzger, Markus T
2017-03-22 17:09 ` Yao Qi
2017-03-23 16:01 ` Metzger, Markus T
2017-03-23 17:25 ` Yao Qi
2017-03-23 18:17 ` Metzger, Markus T
2017-03-24 14:41 ` Yao Qi
2017-03-27 10:51 ` Metzger, Markus T
2017-03-27 11:19 ` Yao Qi
2017-03-27 12:46 ` Metzger, Markus T
2017-03-27 16:03 ` Yao Qi
2017-03-28 7:16 ` Metzger, Markus T
2017-03-28 13:25 ` Yao Qi
2017-03-28 15:08 ` Metzger, Markus T
2017-03-28 15:49 ` Yao Qi
2017-03-29 6:08 ` Metzger, Markus T
[not found] ` <861stgo072.fsf@gmail.com>
2017-03-29 14:38 ` Metzger, Markus T
2017-03-30 10:50 ` Yao Qi
2017-03-30 11:58 ` Metzger, Markus T
[not found] ` <86h92a4w86.fsf@gmail.com>
2017-03-30 15:55 ` Metzger, Markus T
2017-03-31 13:55 ` Yao Qi
2017-03-31 15:21 ` Metzger, Markus T
2017-03-31 16:02 ` Joel Brobecker
2017-04-06 14:40 ` Wiederhake, Tim
2017-04-07 8:10 ` Yao Qi
2017-04-07 11:53 ` Wiederhake, Tim
2017-04-07 15:19 ` Yao Qi
2017-03-21 14:00 ` Yao Qi
2017-03-21 14:03 ` Pedro Alves
2017-03-27 13:35 ` Antoine Tremblay
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=20170320201629.pbjzaqsnvs7dx7f2@adacore.com \
--to=brobecker@adacore.com \
--cc=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=mishra.nitish.88@gmail.com \
--cc=tim.wiederhake@intel.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