GDB 13 release -- 2022-10-29 update

GDB 13 release -- 2022-10-29 update

[Joel Brobecker]

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.

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

Re: GDB 13 release -- 2022-10-29 update

[Andrew Burgess]

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

Re: GDB 13 release -- 2022-10-29 update

[Luis Machado]

Hi Joel,

On 10/29/22 19:51, Joel Brobecker via Gdb-patches wrote:
> 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.
> 
> 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!

I'd like to include https://sourceware.org/bugzilla/show_bug.cgi?id=29738 to the GDB 13 list, which
is still under investigation for a proper fix.

Re: GDB 13 release -- 2022-10-29 update

[Joel Brobecker]

> I'd like to include
> https://sourceware.org/bugzilla/show_bug.cgi?id=29738 to the GDB 13
> list, which is still under investigation for a proper fix.

OK for me, Luis. Thanks for flagging that one.

-- 
Joel