Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: bernd.edlinger@hotmail.de, Joel Brobecker <brobecker@adacore.com>
Subject: GDB 11.1 release prep update (2021-07-11)
Date: Sun, 11 Jul 2021 07:43:51 -0700	[thread overview]
Message-ID: <20210711144351.GC634772@adacore.com> (raw)

Hi everyone,

Here is a quick status of where we are today, in terms of the GDB 11.1
release.

We branched last week (hurray!), and so far, we haven't received news
of any major issues. So we're left with the issues listed below,
with some being absolutely blocking, and others being a bit less so.

For those who have the time and expertise, it would be awesome if
we could prioritize those issues.

Thank you!

---

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

* [SimonM] <PR gdb/28056>
  linux-tdep.c:2550: internal-error: displaced_step_prepare_status linux_displaced_step_prepare on s390x-linux-gnu

        Looks like Simon fixed it, but PR still open. I am guessing
        that was just an oopsie. Wrote Simon to double-check.

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

  * [LuisM] <PR corefiles/27909>
    AArch64 MTE fixes and corefile support
    https://sourceware.org/bugzilla/show_bug.cgi?id=27909

      Status 2021-07-11:
        - 2 patches already approved
        - 1 patch under discussion -- looks like good progress between
          Pedro and Luis:
          https://sourceware.org/pipermail/gdb-patches/2021-July/180747.html
        - 1 patch waiting for review on non-AArch64 part:
          https://sourceware.org/pipermail/gdb-patches/2021-July/180537.html

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

       I'm getting concerned about this one, as there does not seem
       to have been a review on those patches since they were posted
       early June. There was a ping sent on June 29th.

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

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

    Not a blocker for branching, but should be fixed before the release.


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

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

  * [Sergey with Simon as reviewer] <PR tdep/26633>
    Add Z80 CPU support
    https://sourceware.org/bugzilla/show_bug.cgi?id=26633

    Patch submitted at:
    https://sourceware.org/pipermail/gdb-patches/2020-September/172083.html

    (May 24th) High-level pre-review done at:
    https://sourceware.org/pipermail/gdb-patches/2021-May/179191.html

    No movement since then. Not blocking for branching since it would
    be safe to backport after branching. Not blocking for release either.

  * [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-07-11 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11 14:43 Joel Brobecker [this message]
2021-07-11 17:04 ` Jonah Graham
2021-07-11 19:43   ` Jonah Graham
2021-07-12  2:21     ` Jonah Graham
2021-07-12  2:23       ` Jonah Graham
2021-07-12 15:37         ` Jonah Graham
2021-07-12 22:27           ` Jonah Graham
2021-07-13 14:37             ` Joel Brobecker
2021-07-17 14:37 ` Simon Marchi via Gdb-patches

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=20210711144351.GC634772@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gdb-patches@sourceware.org \
    /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