From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Cc: tom@tromey.com
Subject: Re: GDB 10.1 release: branching early July?
Date: Sun, 14 Jun 2020 18:57:30 +0200 [thread overview]
Message-ID: <6efb0ffc54a7ae47f38c1a7b31d7a7b509ff4089.camel@skynet.be> (raw)
In-Reply-To: <0c6438b02672bc1def2bd198f527fa09b06d3cfb.camel@skynet.be>
I have corrected the link for the build-id exec-file-mismatch ...
Philippe
On Sun, 2020-06-14 at 18:53 +0200, Philippe Waroquiers via Gdb-patches wrote:
> On Sat, 2020-06-13 at 18:56 -0700, 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?
> I have a few things that IMO would be nice (or needed) in 10.1:
>
> Default args for alias.
> I have just sent the RFAv7 that implements
> the prevention of an alias of an alias that has default args,
> as suggested by Simon:
> https://sourceware.org/pipermail/gdb-patches/2020-June/169467.html
>
> There are 2 things still to look at for the 'exec-file-mismatch':
>
> * Below fixes a regression due to using build-id in exec-file-mismatch:
> https://sourceware.org/pipermail/gdb-patches/2020-June/169467.html
This is the correct link:
https://sourceware.org/pipermail/gdb-patches/2020-June/169287.html
>
> * an opened PR for which some feedback is needed
> https://sourceware.org/bugzilla/show_bug.cgi?id=25475
> Note that possibly fixing this might change the user visible CLI.
>
> Thanks
> Philippe
>
> NB: I also have an RFC Improve handling of breakpoints with multiple locations.
> https://sourceware.org/pipermail/gdb-patches/2020-May/168921.html
> but no feedback received yet, so better for GDB 11.
>
>
> > 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?
> >
> > Thank you!
next prev parent reply other threads:[~2020-06-14 16:57 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 [this message]
2020-06-16 0:13 ` Joel Brobecker
2020-06-26 11:36 ` Luis Machado
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=6efb0ffc54a7ae47f38c1a7b31d7a7b509ff4089.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).