GDB 13.2 (corrective) release -- 2023-05-05 Update

GDB 13.2 (corrective) release -- 2023-05-05 Update

[Joel Brobecker]

Hi Everyone,

No real change since our last update a week ago: So far, no known
blocking issue that we want to fix before we publish GDB 13.2.

  => Target release date: Sat 27 May 2023.

Please let us know if there are issues that we should consider for
that release.

FTR: List of fixes in GDB 13.2 as of now:
-----------------------------------------

 * PR testsuite/30158 (rustc testsuite fails with 13.1, apparently worked before with trunk 20230114 on i686-linux-gnu and powerpc64le-linux-gnu)
 * PR gdb/30214 (GDB 13.1 does not compile on FreeBSD 13.1)
 * PR gdb/30240 ((linux/aarch) thread.c:86: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed)
 * PR symtab/30357 (Segmentation fault for the 'start' command)
 * PR symtab/30369 ([gdb/symtab] False match issue in skip_prologue_using_linetable)
 * PR gdb/30423 (Build failures with clang 16)

-- 
Joel

Re: GDB 13.2 (corrective) release -- 2023-05-05 Update

[Tom Tromey]

>>>>> "Joel" == Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:

Joel> Hi Everyone,
Joel> No real change since our last update a week ago: So far, no known
Joel> blocking issue that we want to fix before we publish GDB 13.2.

Joel>   => Target release date: Sat 27 May 2023.

Joel> Please let us know if there are issues that we should consider for
Joel> that release.

I think this one would be reasonable:

https://sourceware.org/bugzilla/show_bug.cgi?id=30271

It's a fairly obvious bug in the new scanner.
I wrote a test case and I'm going to check it in on git master soon.

I set the target milestone on the bug but of course we can change it if
need be.

Tom

Re: GDB 13.2 (corrective) release -- 2023-05-05 Update

[Joel Brobecker]

Hi Tom,

> I think this one would be reasonable:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=30271
> 
> It's a fairly obvious bug in the new scanner.
> I wrote a test case and I'm going to check it in on git master soon.
> 
> I set the target milestone on the bug but of course we can change it if
> need be.

Sounds good to me :).

Thanks for highlighting this patch.

-- 
Joel