public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: gdb-7.11.1 - 2 weeks to go...
Date: Tue, 10 May 2016 16:18:00 -0000	[thread overview]
Message-ID: <20160510161756.GB26324@adacore.com> (raw)

Hello everyone,

Just a quick update on this 7.11.1 release - our target release date
is about 2 weeks away. As far as I can tell from looking at...

    https://sourceware.org/gdb/wiki/GDB_7.11_Release

... we have 2 open PRs:

  * Bug 19828 - 7.11 regression: non-stop gdb -p <process from a
    container>: internal error

    Looks already fixed on master, so there is a chance we might
    be able to fix that on the branch soon.

  * Bug 20039 - Using MI/all-stop, can't interrupt multi-threaded
    program after continue

    Looks like this one was already fixed in master as well.
    Should be a matter of backporting the relevant patches, if
    we can confirm they are safe.

So, all in all, we're looking good. If there are other blocking
issues for 7.11.1 that you know about but haven't been identified,
the best way forward is to:

  1. Create a PR
  2. Mention this PR here, so we can confirm with you whether
     the issue is, in fact, deemed blocking or not. If blocking,
     we'll update the PR's target milestone.

Thank you, all.
-- 
Joel

             reply	other threads:[~2016-05-10 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 16:18 Joel Brobecker [this message]
2016-05-19 15:21 ` Pedro Alves
2016-05-20 13:25   ` Joel Brobecker
2016-05-25 15:22     ` Pedro Alves
2016-05-25 17:45       ` Pedro Alves
2016-05-27 14:05         ` Joel Brobecker

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=20160510161756.GB26324@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).