public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: Propose GDB 11 branching next weekend (Jul 03-04, 2021)
Date: Mon, 28 Jun 2021 06:40:40 +0000	[thread overview]
Message-ID: <DM5PR11MB1690810FA831071045F39EEEDE039@DM5PR11MB1690.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210626190100.GA304875@adacore.com>

Hello Joel,

I fixed a few issues in record run-control that cause GDB to hang:
https://sourceware.org/pipermail/gdb-patches/2021-March/177015.html.

It would be nice if they could be included in the next release.  It's a bit
hard to find someone familiar with infrun to review those patches.

Regards,
Markus.

>-----Original Message-----
>From: Gdb-patches <gdb-patches-
>bounces+markus.t.metzger=intel.com@sourceware.org> On Behalf Of Joel
>Brobecker
>Sent: Saturday, June 26, 2021 9:01 PM
>To: gdb-patches@sourceware.org
>Cc: bernd.edlinger@hotmail.de; Joel Brobecker <brobecker@adacore.com>
>Subject: Propose GDB 11 branching next weekend (Jul 03-04, 2021)
>
>Hi everyone,
>
>Below is a detailed update of where we are with the release preparations,
>and in particular, with respect to creating the branch.
>
>In my opinion, we should branch within the next week or two. We haven't
>been able to take care of all the items that we had on our list, but
>it's been a long effort getting to where we are now, and I think none
>of them are critical for branching, and they all seem like it should be
>reasonable to backport the fix to the branch later on. I have a feeling
>it's going to be another few weeks before all release-blocking issues
>are solved, so I'd rather we use a branch to make sure it's stable, now.
>
>That's why I'd like to propose that we create the gdb-11-branch
>this coming weekend (Jul 03-04, 2021).
>
>Any objections or comments?
>
>Thank you!
>
>---
>
>Fixed Since the Previous Update:
>--------------------------------
>
>  * [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
>
>  * [Simon/Andre] <PR gdb/27994>
>    ASan crash when printing expression involving function call
>    https://sourceware.org/bugzilla/show_bug.cgi?id=27994
>
>
>Added Since the Last Update:
>----------------------------
>
>  * [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.
>
>
>Other Ongoing Items:
>--------------------
>
>  * [LuisM] <PR corefiles/27909>
>    AArch64 MTE fixes and corefile support
>    https://sourceware.org/bugzilla/show_bug.cgi?id=27909
>
>  * [HannesD] some Python-suport changes for the TUI interface
>
>    [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)
>
>
>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
>
>  * [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
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  parent reply	other threads:[~2021-06-28  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 19:01 Joel Brobecker
2021-06-27  2:33 ` Simon Marchi
2021-06-28  6:40 ` Metzger, Markus T [this message]
2021-06-28 17:20   ` Joel Brobecker

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=DM5PR11MB1690810FA831071045F39EEEDE039@DM5PR11MB1690.namprd11.prod.outlook.com \
    --to=markus.t.metzger@intel.com \
    --cc=brobecker@adacore.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).