GDB 10.2 release (respin) -- 2021-01-31 Update

[Joel Brobecker]

Hi everyone,

It's been 3 months since our 10.1 release, and we have since then
pushed 8 fixes to the gdb-10-branch, so now is a good time to think
about a corrective release.

The plan would be to create the release as soon as able, so we can
then start thinking about Release 11.1 soon after. For now, here is
a quick status update of the things I know about. Please let me know
if there are other issues that we should consider for this corrective
release.

Thank you!

Fixed Since the Previous Update:
--------------------------------

  N/A for this round (this is the first update for this release ;-) ).

Added Since the Last Update:
----------------------------

  I'll start from the list of bugs filed for 10.2, available via:
  https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&list_id=24362&product=gdb&query_format=advanced&target_milestone=10.2

  * [TomDV/SimonM/PedroA?] <PR remote/26614>
    AddressSanitizer: heap-use-after-free of extended_remote_target in remote_async_inferior_event_handler
    https://sourceware.org/bugzilla/show_bug.cgi?id=26614

    According to the bug, a patch was pushed on Jan 7th.
    Are there other fixes needed for that one, or can we close?
    (I'll ask on the PR)

  * [SimonM] <PR gdb/26828>
    SIGSEGV in follow_die_offset dwarf2/read.c:22950
    https://sourceware.org/bugzilla/show_bug.cgi?id=26828

    I see that Simon posted a patch series that the bug reporter
    confirmed fixes the issue; 2 patches were pushed, and 2 remain.

    [PATCH 3/4] gdb/dwarf: don't enqueue CU in maybe_queue_comp_unit if already expanded
    https://sourceware.org/pipermail/gdb-patches/2021-January/175265.html
    (asking TomT if he has an opinion)

    [PATCH 4/4] gdb/dwarf: create and destroy dwarf2_per_bfd's CUs-to-expand queue
    https://sourceware.org/pipermail/gdb-patches/2020-December/173964.html
    Already approved by TomT

  * [<UNASSIGNED>] <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

    As the subject says, it's an unwinder issue.
    Simon was able to reproduce, and tied this issue to a specific
    commit adding multi-target support.

    It's a 9->10 regression, so it would be nice to fix, but the risk
    at the moment, is that the PR is currently not assigned, so there is
    no "champion" to look after it.

Simon also requested we consider:

  * [SimonM] <PR symtab/26813>
    DW_FORM_rnglistx and DW_FORM_loclistx not fully supported
    https://sourceware.org/bugzilla/show_bug.cgi?id=26813

    Simon posted a patch series on Jan 20th:
    [PATCH 00/13] DWARF 5 rnglists & loclists fixes (PR 26813)
    https://sourceware.org/pipermail/gdb-patches/2021-January/175221.html

Other Ongoing Items:
--------------------

  < none :) >

Not Critical, but Requested:
----------------------------

  < none :) >

-- 
Joel