From: Andrew Burgess <aburgess@redhat.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 13 release -- 2022-10-29 update
Date: Mon, 31 Oct 2022 12:27:14 +0000 [thread overview]
Message-ID: <877d0gch5p.fsf@redhat.com> (raw)
In-Reply-To: <Y112JzTAK4qfzj/S@adacore.com>
Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:
> Hi everyone,
>
> Here is a quick update on all the items currently on our radar
> for GDB 13. Philippe's changes are still waiting for approval.
> It would be nice if someone more current with GDB development
> than I took a look, but if not, I will put it on my list of
> patches to review towards late Nov.
I'd like to add gdb/29712 to the list please. Tom de Vries' part has
been merged. There's a V2 for my work here:
https://sourceware.org/pipermail/gdb-patches/2022-October/193217.html
Thanks,
Andrew
>
> Fixed Since the Previous Update:
> --------------------------------
>
> * [Torbjörn] PR gdb/28549
> ARM/Cortex-M: improper stack unwinding when the target is in lockup state
> https://sourceware.org/bugzilla/show_bug.cgi?id=28549
>
> PR still open, but assume fixed based on Torbjörn's email:
> https://sourceware.org/pipermail/gdb-patches/2022-October/193182.html
>
> * [Torbjörn]
> gdb/arm: Handle lazy FPU state preservation
>
> Added Since the Last Update:
> ----------------------------
>
> * [TomT] PR c++/29243
> infinite loop in generic_value_print
> https://sourceware.org/bugzilla/show_bug.cgi?id=29243
>
> Patch submitted on Oct 18th:
> https://sourceware.org/pipermail/gdb-patches/2022-October/192804.html
> Just approved :).
>
> Other Ongoing Items:
> --------------------
>
> * [PhilippeW]
> Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno
>
> v3 here: https://sourceware.org/pipermail/gdb-patches/2022-June/189824.html
>
> * [TomT] PR symtab/29105
> new DWARF reader still slow
> https://sourceware.org/bugzilla/show_bug.cgi?id=29105
>
> The subject of this PR and the initial message mention that
> the index cache is still faster than the new DWARF reader.
> But reading following discussions, it's not clear to me
> anymore what this ticket is about, or what's left to do.
> I will follow up on the PR itself.
>
> Thank you all!
> --
> Joel
next prev parent reply other threads:[~2022-10-31 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 18:51 Joel Brobecker
2022-10-31 12:27 ` Andrew Burgess [this message]
2022-11-02 16:28 ` Luis Machado
2022-11-02 18:28 ` 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=877d0gch5p.fsf@redhat.com \
--to=aburgess@redhat.com \
--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).