public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 13 release -- 2022-09-25 update
Date: Sun, 25 Sep 2022 17:19:00 -0700	[thread overview]
Message-ID: <YzDv9DZsEYwNwKxk@adacore.com> (raw)

Hello everyone,

Here is the current status of issues that were flagged prior to
GDB 13 branching. Let's also flag issues that we want fixed for
GDB 13, but that aren't necessarily blocking for branching.

One of the patches in the list is PhilippeW's patch, which has
been posted early June, and has received a total of 10 pings :-(.
I think it is fair at this stage to block the release until
the patch is reviewed. Any volunteer?

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

  * [PhilippeW]
    Show locno for 'multi location' breakpoint hit msg+conv var $bkptno $locno

    v3 here: https://sourceware.org/pipermail/gdb-patches/2022-June/189824.html

  * [TomT] PR symtab/29179
    .gdb_index support for Ada
    https://sourceware.org/bugzilla/show_bug.cgi?id=29179

    TomT sent a patch:
    https://sourceware.org/pipermail/gdb-patches/2022-September/192056.html

Thank you!
-- 
Joel

                 reply	other threads:[~2022-09-26  0:19 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=YzDv9DZsEYwNwKxk@adacore.com \
    --to=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).