From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 10.2 Release: Proposing Mar 13-14 for official GDB 10.2 release
Date: Tue, 9 Mar 2021 00:08:19 -0500 [thread overview]
Message-ID: <06d96113-d09b-993f-0f55-00c297b4e591@simark.ca> (raw)
In-Reply-To: <20210306064611.GB807147@adacore.com>
On 2021-03-06 1:46 a.m., Joel Brobecker wrote:
> Hello everyone,
>
> Thanks again to everyone who's been helping on this release so far.
> See the summary below, where we only have 2 patches left to backport.
>
> Unless there are any issues that we're discovering last minute,
> I propose we create the release sometime next weekend:
>
> 13-14 March
>
> Cheers!
>
> Fixed Since the Previous Update:
> --------------------------------
>
> * [<Simon + Andrew>] <PR backtrace/27147>
> [GNU/Linux, sparc64] GDB is unable to print full stack trace (got "previous frame inner to this frame" errors)
> https://sourceware.org/bugzilla/show_bug.cgi?id=27147
>
> * [KeithS] <PR gdb/27333>
> [dwarf-5] abort on unhandled DW_TAG_type_unit in process_psymtab_comp_unit
> https://sourceware.org/bugzilla/show_bug.cgi?id=27333
>
> Added Since the Last Update:
> ----------------------------
>
> * [KevinB] <**PR MISSING**>
> Fix aarch64-linux-hw-point.c build problem with glibc-2.33
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=665af52ec2a52184d39a76d6e724fa4733dbab3c
>
> Already in master. Needs a PR to be created, before the patches
> can be backported.
>
> * [KevinB] <**PR MISSING**>
> amd64-linux-siginfo.c: Adjust include order to avoid gnulib error
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=8488c357ce4fc309d49c7b0224cf9574b68e8116
>
> Already in master. Needs a PR to be created, before the patches
> can be backported.
>
> Other Ongoing Items:
> --------------------
>
> < none :) >
>
> Not Critical, but Requested:
> ----------------------------
>
> < none :) >
>
> Thank you!
>
A new issue has popped up:
https://sourceware.org/bugzilla/show_bug.cgi?id=27541
Tom Tromey and I would be good candidates to look a it,
because it's related to the DWARF symbol sharing, which
we've both worked on. I will try to give it a look in
the following days.
Simon
next prev parent reply other threads:[~2021-03-09 5:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 6:46 Joel Brobecker
2021-03-06 18:13 ` Kevin Buettner
2021-03-07 5:45 ` Joel Brobecker
2021-03-07 6:25 ` Kevin Buettner
2021-03-09 5:08 ` Simon Marchi [this message]
2021-03-10 2:48 ` Joel Brobecker
2021-03-15 3:43 ` Simon Marchi
2021-03-16 3:45 ` Joel Brobecker
2021-03-30 5:02 ` Tom Tromey
2021-03-30 7:59 ` Joel Brobecker
2021-03-30 17:40 ` Simon Marchi
2021-03-30 15:14 ` Simon Marchi
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=06d96113-d09b-993f-0f55-00c297b4e591@simark.ca \
--to=simark@simark.ca \
--cc=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).