From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@arm.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org,
torbjorn.svensson@foss.st.com
Subject: Re: [branching soon!] GDB 13 release -- 2022-12-04 update
Date: Fri, 09 Dec 2022 14:30:04 +0200 [thread overview]
Message-ID: <83tu24zrn7.fsf@gnu.org> (raw)
In-Reply-To: <eb8d6b3d-0c01-7b8e-95cc-d2fa974d35a8@arm.com> (message from Luis Machado via Gdb-patches on Fri, 9 Dec 2022 11:14:17 +0000)
> Date: Fri, 9 Dec 2022 11:14:17 +0000
> Cc: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
>
> Hi Joel,
>
> Thanks for the update.
>
> On 12/4/22 04:33, Joel Brobecker via Gdb-patches wrote:
> > Hello,
> >
> > *GREAT* progress with the list of issues that were addressed last week,
> > as you'll see in the summary below. Thanks to everyone who helped with
> > that strong push!
> >
> > We're down to one issue left, which have been under discussion.
> > Hopefully we converge soon. Otherwise, I propose we still go ahead
> > and branch, and we'll look at backporting the fix to the branch
> > once it is available.
> >
> > Based on the above, I propose we aim for branching next weekend,
> > Sat-Sun Dec 10-11.
> >
> > Thanks again, everyone.
> >
> > Fixed Since the Previous 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
> >
> > * [TomT] PR symtab/29105
> > new DWARF reader still slow
> > https://sourceware.org/bugzilla/show_bug.cgi?id=29105
> >
> > * [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
> >
> > * [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
> >
> > * [TomT] cli/29800
> > Trying to "document" an undefined command causes crash
> > https://sourceware.org/bugzilla/show_bug.cgi?id=29800
> >
> > Added Since the Last Update:
> > ----------------------------
> >
> > < none :) >
> >
> > Other Ongoing Items:
> > --------------------
> >
> > * [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
> >
What is the decision regarding target-async support on MS-Windows?
Will it be in GDB 13 or will it be deferred to GDB 14?
next prev parent reply other threads:[~2022-12-09 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 4:33 Joel Brobecker
2022-12-04 15:45 ` Tom Tromey
2022-12-05 3:19 ` Joel Brobecker
2022-12-05 20:43 ` Tom Tromey
2022-12-06 5:25 ` Joel Brobecker
2022-12-09 11:14 ` Luis Machado
2022-12-09 12:30 ` Eli Zaretskii [this message]
2022-12-09 13:23 ` Joel Brobecker
2022-12-09 14:54 ` Eli Zaretskii
2022-12-09 15:03 ` 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=83tu24zrn7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=torbjorn.svensson@foss.st.com \
/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).