From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 13 release -- 2022-10-09 Update
Date: Sun, 9 Oct 2022 16:57:32 -0700 [thread overview]
Message-ID: <Y0Nf7Kxhj861URVc@adacore.com> (raw)
Hello,
Here is a quick update on all the items currently on our radar
for GDB 13.
Fixed Since the Previous Update:
--------------------------------
<none>
Added Since the Last 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
Seems like there is a set of patches, but not entirely clear on
where the latest version is located, and whether they have been
approved or not.
Seems to be blocked by FSF copyright assignment paperwork.
I will ask for the motivations behind requesting this patch be
included in GDB 13.
* [Torbjörn]
gdb/arm: Handle lazy FPU state preservation
Patch has been approved by Luis; open question about whether
we can accept it or not (FSF copyright assignment).
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.
* [TomT] PR symtab/29106
new DWARF reader should de-duplicate functions
https://sourceware.org/bugzilla/show_bug.cgi?id=29106
* [TomT] PR symtab/29179
.gdb_index support for Ada
https://sourceware.org/bugzilla/show_bug.cgi?id=29179
TomT sent a patch:
https://sourceware.org/pipermail/gdb-patches/2022-September/192056.html
--
Joel
reply other threads:[~2022-10-09 23:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y0Nf7Kxhj861URVc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).