GDB 12 preparation -- 2022-03-06 update

GDB 12 preparation -- 2022-03-06 update

[Joel Brobecker]

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

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


Reminder: Tentative Schedule:
-----------------------------

  - GDB 12 branching: ~Mar 20-25;
  - GDB 12.1 release 2 weeks later, so early Apr.

-- 
Joel

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

[Luis Machado]

On 3/6/22 10:15, Joel Brobecker via Gdb-patches wrote:
> 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).

I think this would be nice to fix it for GDB 12 (it is potentially a 
small fix), but not critical enough to stop a release. It's been there 
for a while after all.

Feel free to drop it from the blockers list. I opened this last year, 
but I couldn't finish it due to outstanding circumstances, sorry.

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

[Joel Brobecker]

> > 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).
> 
> I think this would be nice to fix it for GDB 12 (it is potentially a small
> fix), but not critical enough to stop a release. It's been there for a while
> after all.
> 
> Feel free to drop it from the blockers list. I opened this last year,
> but I couldn't finish it due to outstanding circumstances, sorry.

Understood, and no worries at all. I'm just gathering information
is all ;-). I removed the target milestone for now, with the
understanding that depending on the nature of the patch, there is
always a chance of it either making it to master before the branch
is cut, or else for it to be backported if appropriate.

Thanks Luis!
-- 
Joel

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

[Tom Tromey]

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

Joel> Added Since the Last Update:
Joel> ----------------------------
Joel>   <none>

I'd like to add the --dbx deprecation patch.

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

I sent a note to the main gdb list.  I suppose we could simply check it
in now and back it out before 12 if there are strong objections.  WDYT?

Tom

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

[Andrew Burgess]

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

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

[Joel Brobecker]

Hi Tom,

> Joel> Added Since the Last Update:
> Joel> ----------------------------
> Joel>   <none>
> 
> I'd like to add the --dbx deprecation patch.
> 
> https://sourceware.org/pipermail/gdb-patches/2022-March/186306.html
> 
> I sent a note to the main gdb list.  I suppose we could simply check it
> in now and back it out before 12 if there are strong objections.  WDYT?

No problem with me. I doubt anyone will object, so I vote for
adding the deprecation note now. Like you say, if there are
objections, it's really easy to back out.

-- 
Joel

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

[Joel Brobecker]

> >   * 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.

Perfect. Thanks for the pointers, Andrew. And of course, for your help
on that one too!

-- 
Joel

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

[Tom Tromey]

Joel> No problem with me. I doubt anyone will object, so I vote for
Joel> adding the deprecation note now. Like you say, if there are
Joel> objections, it's really easy to back out.

Ok, I'm going to push it now.  I have a removal patch ready as well, but
that can wait until the branch.

Tom