Re: GDB 12 preparation -- 2022-03-06 update

[Andrew Burgess <aburgess@redhat.com>]

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

> Hi everyone,
>
> We are making very good progress, it seems, on the two issues
> we have identified for GDB 12, so if things continue this way,
> we might be on track to create our first pre-release around
> the time we were targetting, which is March 20-25 (repeated
> at the end of every message, just for the record)!
>
> There has also been ...
>
>     https://sourceware.org/bugzilla/show_bug.cgi?id=28616
>
> ... where I wasn't sure why it was marked GDB 12, and have been
> trying to reach out to the person who created the PR. I've tried
> a different email which I think will work. Given that I'm not
> seeing progress on this PR either, I'm hoping this one isn't
> going to be deemed critical (it does seem to happen in unusual
> circumstances, but workarounds once hist are unclear at the moment).
>
> That's it for this week. Let's see where we're at at the end
> of next week :).
>
> ---
>
> 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

I've posted this series to the gdb list:

  https://sourceware.org/pipermail/gdb-patches/2022-March/186391.html

that fixes bug 28833.  There's a backport from readline, plus a GDB fix
to use the new readline features.

Thanks,
Andrew