From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, sergiodj@redhat.com,
Yao Qi <yao@codesourcery.com>, Pedro Alves <palves@redhat.com>,
keiths@redhat.com
Subject: RFC: branching for GDB 7.11 soon? (possibly Wed)
Date: Mon, 01 Feb 2016 03:06:00 -0000 [thread overview]
Message-ID: <20160201030638.GG4008@adacore.com> (raw)
Hello everyone,
According to the GDB 7.11 release cycle wiki page
(https://sourceware.org/gdb/wiki/GDB_7.11_Release),
there no longer any items that are explicitly marked as being
blocking for branching. We do have a few "maybe"-s. There are also
3 PRs filed with a target-milestone of GDB 7.11. From experience,
if we want them to make a given release, they need to have a champion.
Currently unassigned, we have:
PR19474 "break LINE_NUM" set breakpoint on file other than current source file
(suggest Keith?)
PR19503 internal-error: linux_nat_resume: Assertion `lp != NULL' failed.
(Pedro seems to be on it already)
In addition, we have the following PR, which Keith already sent
a patch:
PR19506 Regression with gdb.Breakpoint("*<addr>")
At the moment, I would be hesitant to branch before we first
analyze what would be required to fix PR19474 ("break LINE_NUM").
But if we're confident that it can be fairly safely fixed on
the branch, I don't see any other issue blocking for branching,
which I would then propose to be doing sometime early Wed.
Sergio - would you be able to give us a rough description of how
good the results are in the buildbots? Anything we should be
aware of for this release? (Thanks!)
Thoughts?
--
Joel
next reply other threads:[~2016-02-01 3:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 3:06 Joel Brobecker [this message]
2016-02-01 13:34 ` Pedro Alves
2016-02-01 17:04 ` Pedro Alves
2016-02-01 19:51 ` Keith Seitz
2016-02-04 0:45 ` [RFC] breakpoints/19474 [was Re: RFC: branching for GDB 7.11 soon? (possibly Wed)] Keith Seitz
2016-02-04 1:33 ` Keith Seitz
2016-02-04 11:05 ` Yao Qi
2016-02-04 12:31 ` Pedro Alves
2016-08-12 12:00 ` Yao Qi
2016-02-07 8:12 ` RFC: branching for GDB 7.11 soon? (possibly Wed) Joel Brobecker
2016-02-08 18:03 ` Sergio Durigan Junior
2016-02-08 19:28 ` Keith Seitz
2016-02-08 20:06 ` Pedro Alves
2016-02-08 20:11 ` Keith Seitz
2016-02-09 5:35 ` Sergio Durigan Junior
2016-02-09 14:15 ` Simon Marchi
2016-02-09 14:18 ` Pedro Alves
2016-02-09 14:52 ` Simon Marchi
2016-02-09 18:31 ` Sergio Durigan Junior
2016-02-09 11:56 ` Joel Brobecker
2016-02-09 12:37 ` Pedro Alves
2016-02-09 22:37 ` Keith Seitz
2016-02-10 3:40 ` Joel Brobecker
2016-02-10 10:04 ` Pedro Alves
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=20160201030638.GG4008@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
--cc=yao@codesourcery.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