Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Cc: tom@tromey.com
Subject: Re: GDB 10.1 release: branching early July?
Date: Fri, 26 Jun 2020 08:36:36 -0300	[thread overview]
Message-ID: <efe3a0e9-e964-393f-5a11-bd75ffe0877a@linaro.org> (raw)
In-Reply-To: <20200614015612.GA6242@adacore.com>

On 6/13/20 10:56 PM, Joel Brobecker wrote:
> Hi everyone,
> 
> Now that the GDB 9.2 release has been out for a few weeks, what
> do you think about turning our attention to starting the GDB 10
> release cycle?  I looked at the NEWS file, and there is a decent
> number of new features.
> 
> Based on that, what do you think of aiming for branching during
> the weekend of July 4th? That's 3 weeks from now. We would then
> be creating the first pre-release at the same time if possible,
> and then try to aim for a release 2-3 weeks afterwards.
> 
> Are there any changes that you think we should have in master
> before we create the branch?
> 
> This is what is current in the 10.1 list on Bugzilla:
> 
>    * [unassigned]
>      <PR gdb/25412> thread_info with duplicate ptid added to inferior thread list
>      https://sourceware.org/bugzilla/show_bug.cgi?id=25412
> 
>      Reported by Simon, who started investigating a bit.
>      Simon says the issue appeared after the "multi-target" patch
>      series went in (5b6d1e4fa by Pedro).
> 
>      Simon - is that still an issue?
> 
>    * [RainerO]
>      <PR gdb/25939> [10 regression] run fails with ICE on Solaris
> 
>      Not sure if this is still an issue or not. Rainer did push some
>      patches to master back in May. To be confirmed.
> 
> I also know of the following issue which I think should get fixed
> before we branch:
> 
>    * [AndrewB/TomT]
>      QEMU / GDB compatibility on RISCV64 ELF (failure to fetch some registers)
>      https://sourceware.org/pipermail/gdb-patches/2020-June/169393.html
> 
> Anything else you think we should include?

I just reported one for 10.1, so we can make sure that is fixed before 
branch/release.

https://sourceware.org/bugzilla/show_bug.cgi?id=26175


  parent reply	other threads:[~2020-06-26 11:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  1:56 Joel Brobecker
2020-06-14  2:04 ` Simon Marchi
2020-06-15 22:53   ` Joel Brobecker
2020-06-18 19:57     ` Pedro Alves
2020-06-14 15:14 ` Rainer Orth
2020-06-15 23:09   ` Joel Brobecker
2020-06-16 13:49     ` Rainer Orth
2020-06-16 18:13       ` Joel Brobecker
2020-06-14 15:32 ` Hannes Domani
2020-06-15 23:17   ` Joel Brobecker
2020-06-16 20:28     ` Tom Tromey
2020-06-14 16:53 ` Philippe Waroquiers
2020-06-14 16:57   ` Philippe Waroquiers
2020-06-16  0:13     ` Joel Brobecker
2020-06-26 11:36 ` Luis Machado [this message]
2020-06-26 16:26   ` Joel Brobecker
2020-06-26 19:27     ` Luis Machado

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=efe3a0e9-e964-393f-5a11-bd75ffe0877a@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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