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-11-26 update
Date: Sat, 26 Nov 2022 18:38:04 +0400	[thread overview]
Message-ID: <Y4IkzNZL27UlPJ3Q@adacore.com> (raw)

Hello everyone,

Here is another update of where we are with respect to the GDB 13
release.

As you guys can see, there is definite progress almost each week,
but despite this, new entries arrive, or old ones seem to take quite
a while, resulting in a good number of issues left for us to fix.
At some point, I think we'll need to draw a line at some point,
and take some measures towards at least branching.

Let's say we give it another two weeks for the issues below.
When the two weeks are up, we should start discussing the remaining
issues to see which ones we anticipate can be fixed post branch,
vs which ones (hopefully none) must be fixed prior to branching.

I think we also need to start becoming stricter in our evaluation
of what issues we need to fix prior to GDB 13 branching, and prior
to GDB 13 release.

As always, do not hesitate to send comments, suggestions, etc.

--

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

  * [RainerO] PR build/29791
    Many gdbsupport files don't compile on Solaris
    https://sourceware.org/bugzilla/show_bug.cgi?id=29791

    PR still open, but kept open for reasons independent of
    the GDB 13 release.

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

  * [SimonM[ PR gdb/28275
    commit_resumed_state assertion failure when killing running inferior and running again
    https://sourceware.org/bugzilla/show_bug.cgi?id=28275

    patch series v2 (2022-11-22):
    https://sourceware.org/pipermail/gdb-patches/2022-November/194035.html

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

  * [TomT] PR symtab/29105
    new DWARF reader still slow
    https://sourceware.org/bugzilla/show_bug.cgi?id=29105

    Not sure where we're at with this PR - I will ask Tom when I next
    talk to him.

  * [TomDV,AndrewB] PR python/29712
    UNRESOLVED: gdb.python/py-disasm.exp: global_disassembler=ReadMemoryGdbErrorDisassembler: disassemble test
    https://sourceware.org/bugzilla/show_bug.cgi?id=29712

    TomDV's patches are in. Andrew's latest version (v3, 2022-11-18)
    posted there:
    https://sourceware.org/pipermail/gdb-patches/2022-November/193983.html

  * [Torbjorn] tdep/29738
    Arm M-profile dwarf2 unwinder performance suffers from exponential growth
    https://sourceware.org/bugzilla/show_bug.cgi?id=29738

    patch v2, 2022-11-18, reviewed 2022-11-21:
    https://sourceware.org/pipermail/gdb-patches/2022-November/193960.html

  * [TomT] PR gdb/29787
    Bug 29787 - Using "set debug infrun on" and "set logging enabled" breaks GDB prompt and makes GDB crash
    https://sourceware.org/bugzilla/show_bug.cgi?id=29787

    Patch submitted for review 2022-11-17:
    https://sourceware.org/pipermail/gdb-patches/2022-November/193923.html

  * [TomT] cli/29800
    Trying to "document" an undefined command causes crash
    https://sourceware.org/bugzilla/show_bug.cgi?id=29800

    Patch submitted for review 2022-11-18, approved:
    https://sourceware.org/pipermail/gdb-patches/2022-November/193967.html

Thanks,
-- 
Joel

             reply	other threads:[~2022-11-26 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 14:38 Joel Brobecker [this message]
2022-11-28 14:41 ` Tom Tromey
2022-11-28 19:20 ` Simon Marchi

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=Y4IkzNZL27UlPJ3Q@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).