Re: GDB 12 branching next weekend (2022-03-20 or 2022-03-21)?

[Andrew Burgess <aburgess@redhat.com>]

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

> Hi everyone,
>
> Given the advancement on the two remaining items identified for
> the GDB 12 release, I think we can shoot for branching this coming
> weekend:
>
>         Sat/Sun March 20-21.
>
> If you guys see some issues with that, then please let us know.
> Otherwise, let's go for it!
>
> Cheers everyone.
>
> ---
>
> Fixed Since the Previous Update:
> --------------------------------
>
>   <none>
>
>
> Added Since the Last Update:
> ----------------------------
>
>   <none>
>
>
> Other Ongoing Items:
> --------------------
>
>   * TBC: [BarisA/AndrewB] <PR cli/28833>
>     Ctrl-D distorts GDB prompt
>     https://sourceware.org/bugzilla/show_bug.cgi?id=28833
>
>
>         Baris requested that we consider the bug above, which seems
>         to be a GDB 11 regression for Baris.
>
>         IIUC, Andrew fixed the issue in upstream's readline, and
>         now we just need to backport it.
>         https://lists.gnu.org/archive/html/bug-readline/2022-03/msg00005.html
>
>         Backport request on GDB ml:
>         https://sourceware.org/pipermail/gdb-patches/2022-March/186391.html
>
>         There was a suggestion that we use a more limited bug safer
>         approach for GDB 12. I did not look at the patch, but if it
>         helps make people more comfortable, this seems like a valid
>         approach.

I've now pushed the more limited work around for this issue, which
should be good enough for GDB 12 (unless anyone wants to argue in favour
of the full fix making the release).

>
>   * [AndrewB] create GDB/MI commands using python
>
>         Explicit request to include in GDB 12; accepted as the patches
>         were sent prior to the start of the GDB 12 release process.
>
>         Latest version (v5) pasted by Andrew, and approved by Tom:
>         https://sourceware.org/pipermail/gdb-patches/2022-February/186176.html
>
>         Let's push the patch ;-).

This is now pushed.

Thanks,
Andrew