public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	tdevries@suse.de, ssbssa@yahoo.de, simon.marchi@polymtl.ca,
	bernd.edlinger@hotmail.de, philippe.waroquiers@skynet.be
Subject: GDB 11.1 release prep update (2021-08-24)
Date: Tue, 24 Aug 2021 07:43:22 -0700	[thread overview]
Message-ID: <20210824144322.GA518970@adacore.com> (raw)

Hi everyone,

Here is another status update, showing that we are slowly but surely
making progress, and I think we should plan on the release being made
sometime around mid September.

The following items have made no progress for several months, now,
with the onus being on the contributor; at this point, I think
we should exclude them from the release:
  * [HannesD] some Python-suport changes for the TUI interface
  * gdb on OSX Mojave hangs in darwin_decode_message
  * [BerndE] Improve debugging of optimized code
  * Follow-up on x86-64 stub submission

For Philippe's contribution (Fix/complete option list/description in
manual and in gdb --help), it's on us Global Maintainers to review
the patch; but on the other hand, I don't think this is critical either.
Worse case, we can always backport to the .2 if felt important enough.

And then there's one new PR where we have a proposed patch, but
I'm not sure yet whether it should be deemed blocking or not. TBD.

So, with all the above said, I hope that we'll be OK to create
the release within the next two weeks.

Thanks all!

---

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

  * [TomDV] <PR varobj/28131>
    Segfault in gdbpy_enter_varobj::gdbpy_enter_varobj when debugging in VS Code
    https://sourceware.org/bugzilla/show_bug.cgi?id=28131

  * [TomDV/Simon] <PR gdb/28004>
    DW_AT_ranges with form DW_FORM_sec_offset problem
    https://sourceware.org/bugzilla/show_bug.cgi?id=28004

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

  * [TomT] <PR symtab/28200>
    DW_AT_ranges handling in partial_die_info::read does not handle discontinuous ranges
    https://sourceware.org/bugzilla/show_bug.cgi?id=28200

    I asked to confirm the reasons was marked with a 11.1 milestone,
    which normally signals that we want to fix this before 11.1 is
    released.

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

  * [HannesD] some Python-suport changes for the TUI interface

       I'm getting concerned about this one, as there is currently
       little activity on them.

    [PATCHv2 1/2] Implement locals TUI window
    https://sourceware.org/pipermail/gdb-patches/2021-June/179539.html
    (I think this patch should provide more information in the commit
    message about what its goal is)

    [PATCHv2 2/2] Use method children instead of to_string in pretty printers
    https://sourceware.org/pipermail/gdb-patches/2021-June/179540.html
    (same suggestion)
    2021-07-17: JoelB did a review, and had one comment.


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

  * [SimonM as awesome supporter and reviewer] <PR gdb/24069>
    gdb on OSX Mojave hangs in darwin_decode_message
    https://sourceware.org/bugzilla/show_bug.cgi?id=24069

        I know that the state of GDB on MacOS is very poor at the moment,
        and so having this PR fixed for 11.1 would be very nice. I don't
        think this PR should block the release, though. This is not new,
        and I'm not sure whether we can expect for us to converge without
        too much delay. There are good signs, though, with regular
        activity on the PR, lately. So let's see how it goes...

  * [BerndE] Improve debugging of optimized code
    https://sourceware.org/pipermail/gdb-patches/2021-January/175617.html

    (2021-05-31) v2 posted at:
      [0/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179367.html
      [1/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179368.html
      [2/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179370.html
      [3/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179369.html


  * [Simon] <PR gdb/26868>
    Follow-up on x86-64 stub submission
    https://sourceware.org/bugzilla/show_bug.cgi?id=26868

    This is the submission in question:
    https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html

    For me, although I am not a lawyer, I don't think we can accept
    the contribution without the author signing a copyright assignment
    form.

  * [PhilippeW] Fix/complete option list/description in manual and in gdb --help

    RFA v2 (2021-06-20):
        [RFAV2] Fix/complete option list/description in manual and in gdb --help.
        https://sourceware.org/pipermail/gdb-patches/2021-June/180186.html


-- 
Joel

             reply	other threads:[~2021-08-24 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 14:43 Joel Brobecker [this message]
2021-08-29 15:58 ` Philippe Waroquiers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210824144322.GA518970@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    --cc=simon.marchi@polymtl.ca \
    --cc=ssbssa@yahoo.de \
    --cc=tdevries@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).