public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: simon.marchi@polymtl.ca, bernd.edlinger@hotmail.de,
	tdevries@suse.de, kevinb@redhat.com, ro@CeBiTec.Uni-Bielefeld.DE,
	luis.machado@linaro.org, Joel Brobecker <brobecker@adacore.com>
Subject: GDB 11 branching update (2021-06-06)
Date: Sun, 6 Jun 2021 08:09:30 -0700	[thread overview]
Message-ID: <20210606150930.GA580376@adacore.com> (raw)

Hello everyone,

Here is another update about the GDB 11 branching. We're making
progress, thanks guys! :-)

Thanks to Andrew's analysis on PR gdb/26819 (RISC-V: internal-error:
int finish_step_over [...]), we found that this is not blocking for
GDB 11 branching or release, so I removed it from the list.

I moved PR tdep/26633 (add Z80 support) to the nice-to-have section.
It was initially in the "ongoing" section on the premise that the patch
had been submitted a while ago and therefore deserved to be considered
for GDB 11. However, I'm not seeing activity from the author, and
the patch adds a new feature, so we shouldn't block the release for it.

I also moved PR gdb/26868 (Follow-up on x86-64 stub submission) to
the nice-to-have section; it's not critical, since this patch adds
a new feature, and seems blocked due to lack of copyright assignment.


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

  * [SimonM] <PR python/27841>
    Failed assertion: assigning convenience variable during inferior exit Python event
    https://sourceware.org/bugzilla/show_bug.cgi?id=27841


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

  * [Bernd/PedroA/TomT] TUI issues from mouse-support patch
    https://sourceware.org/pipermail/gdb-patches/2021-June/179541.html


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

  * [TomDV] <PR symtab/26327>
    GDB hangs in get_builder() due to recursive ancestor pointers
    https://sourceware.org/bugzilla/show_bug.cgi?id=26327

    There was a patch, but it caused some regressions, and thus
    it has been reverted, making us reopen this PR.

    One comment (May 21st) in the PR says:
    | The problem is not that we search ancestors, the problem is that
    | we allow ancestors to form a loop.  See detailed investigation at
    | <URL: https://bugzilla.opensuse.org/show_bug.cgi?id=1185800 >.  Your
    | fix looks more like a band-aid to me.

  * [Simon/Kevin] <PR gdb/27526>
    Attaching to threaded process on glibc 2.33: libthread_db fails to initialize with "generic error"
    https://sourceware.org/bugzilla/show_bug.cgi?id=27526

    Patch v2 at...
    https://sourceware.org/pipermail/gdb-patches/2021-May/178485.html

    ... approved by Kevin at:
    https://sourceware.org/pipermail/gdb-patches/2021-June/179559.html

    ... But Kevin indicates there are other issues he needs looking at
    for which he hopes to send patches for next week.

  * [RainerO] <PR binutils/27666>
    ar doesn't create indices on Solaris/sparcv9
    https://sourceware.org/bugzilla/show_bug.cgi?id=27666

    Causes large number of tests to fail in gdb's testsuite.

    Patch has been proposed by NickC (uploaded to bugzilla),
    tested by RainerO (2021-06-01) with unfortunately mixed results.
    Worse case scenario, we can branch and then revert the binutils
    patch that caused the issue.

  * [Simon] <PR gdb/27899>
    [GNU/Linux, sparc64] GDB crashes when debugging multithreaded programs
    https://sourceware.org/bugzilla/show_bug.cgi?id=27899

    Patch posted at:
    https://sourceware.org/pipermail/gdb-patches/2021-May/179382.html

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


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

  * [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
      [4/4] https://sourceware.org/pipermail/gdb-patches/2021-May/179371.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.

Thank you!
-- 
Joel
-- 
Joel

                 reply	other threads:[~2021-06-06 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210606150930.GA580376@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bernd.edlinger@hotmail.de \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=luis.machado@linaro.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    --cc=simon.marchi@polymtl.ca \
    --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).