From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Cc: antoine.tremblay@ericsson.com, mishra.nitish.88@gmail.com
Subject: GDB 8.0 release / imminent branching? (2017-04-10)
Date: Tue, 11 Apr 2017 01:18:00 -0000 [thread overview]
Message-ID: <20170411011802.s24zz4pygnt2qoyg@adacore.com> (raw)
Hello,
We're now about 4 weeks after our tentative branching date, and
I am concerned that if we continue to wait for some of the pending
issues to be resolved, we'll have new issues appearing on master
that'll might delay the branching further. So I'd like to propose
we branch in the next couple of days, and then backport fixes,
so as to stabilize the branch.
We have two 8.0 pending PRs:
* server/21169 GDBServer on ARM can crash the inferior while single stepping
Antoine indicated that he's working on it, and his expected
completion date isn't all that far away. Still on track for
that, Antoine?
* build/21187 Static linking of libstdc++ and libgcc with GDB leads to broken exception handling on AIX platform
For this one, I think the feedback so far is a question about
the fact that this is only a work around. Parallel to that,
did I see a thread where people are discussing a real fix
for the exception handling issue?
So, perhaps we might not need the GDB patch after all?
Is there a version of GCC capable of compiling GDB 8.x
on AiX?
Then, there is the issue of the Python APIs for record and btrace.
It sounds like we're getting close? Perhaps what we could do is
also backport the changes once the an agreement has been reached?
And finally, there is the build-bot. I'm having trouble using
the interface and understanding whether the current overall
state is rather positive or negative. Sergio, would you be able
to help me? If all good, I could create the branch with a SHA1
that you'd give me!
Thank you!
--
Joel
next reply other threads:[~2017-04-11 1:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 1:18 Joel Brobecker [this message]
2017-04-11 7:47 ` Yao Qi
2017-04-11 14:21 ` Andreas Arnez
2017-04-11 15:39 ` Yao Qi
2017-04-12 15:38 ` Joel Brobecker
2017-04-11 15:41 ` Eli Zaretskii
2017-04-12 14:18 ` Joel Brobecker
2017-04-11 19:00 ` Antoine Tremblay
2017-04-12 5:27 ` 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=20170411011802.s24zz4pygnt2qoyg@adacore.com \
--to=brobecker@adacore.com \
--cc=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=sergiodj@redhat.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