Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: start of the GDB 11 release cycle
Date: Sun, 9 May 2021 17:04:48 -0700	[thread overview]
Message-ID: <20210510000448.GA4371@adacore.com> (raw)

Hello,

It's been about 6.5 months since we made the first GDB 10 release (10.1).
So I propose we start the process of creating the GDB 11 release now.

As of now, below are the issues that I'm aware of:

  * [Sergey with Simon as reviewer] <PR tdep/26633>
    Add Z80 CPU support
    https://sourceware.org/bugzilla/show_bug.cgi?id=26633

    Patch submitted at:
    https://sourceware.org/pipermail/gdb-patches/2020-September/172083.html

  * [AndrewB/Simon] <PR gdb/26819>
    Bug 26819 - RISC-V: internal-error: int finish_step_over(execution_control_state*): Assertion
    https://sourceware.org/bugzilla/show_bug.cgi?id=26819

    I think the situation has been improved thanks to a couple of
    patches, but the user still has some scenarios where the issue
    happens.

  * [Simon] <PR gdb/26868>
    Follow-up on x86-64 stub submission
    https://sourceware.org/bugzilla/show_bug.cgi?id=26868

    This is the submission in question:
    https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html

  * [Simon/Kevin] <PR gdb/27526>
    Attaching to threaded process on glibc 2.33: libthread_db fails to initialize with "generic error"

    Patch v2 at:
    https://sourceware.org/pipermail/gdb-patches/2021-May/178485.html

Are there other issues or last minute features we'd like to include
before we branch and/or release?

Thank you!
-- 
Joel

             reply	other threads:[~2021-05-10  0:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  0:04 Joel Brobecker [this message]
2021-05-10  3:20 ` Mike Frysinger via Gdb-patches
2021-05-10 22:10   ` Joel Brobecker
2021-05-24 19:40   ` Joel Brobecker
2021-05-25  2:01     ` Mike Frysinger via Gdb-patches
2021-05-26 22:03       ` Joel Brobecker
2021-05-29 15:58         ` Mike Frysinger via Gdb-patches
2021-05-10  3:52 ` Luis Machado via Gdb-patches
2021-05-10 22:11   ` Joel Brobecker
2021-05-11 11:05     ` Luis Machado via Gdb-patches
2021-05-11 17:00       ` Joel Brobecker
2021-05-12 18:15         ` Luis Machado via Gdb-patches
2021-05-24 19:42   ` Joel Brobecker
2021-05-24 20:27     ` Luis Machado via Gdb-patches
2021-05-24 21:02       ` Joel Brobecker
2021-05-25 10:46         ` Luis Machado via Gdb-patches
2021-05-26 22:04           ` Joel Brobecker
2021-05-10  5:52 ` Bernd Edlinger
2021-05-10 15:10   ` Simon Marchi via Gdb-patches
2021-05-10 16:07     ` Andrew Burgess
2021-05-10 16:57       ` Simon Marchi via Gdb-patches
2021-05-10 22:12   ` Joel Brobecker
2021-05-11 12:45 ` Rainer Orth
2021-05-11 16:57   ` 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=20210510000448.GA4371@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