From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [branching soon!] GDB 13 release -- 2022-12-04 update
Date: Mon, 5 Dec 2022 07:19:11 +0400 [thread overview]
Message-ID: <Y41jL16V84Ok1kx3@adacore.com> (raw)
In-Reply-To: <87y1rn9nq1.fsf@tromey.com>
Hi Tom,
> Joel> We're down to one issue left, which have been under discussion.
> Joel> Hopefully we converge soon. Otherwise, I propose we still go ahead
> Joel> and branch, and we'll look at backporting the fix to the branch
> Joel> once it is available.
>
> I hate to say it but I wonder if we should add the Windows target-async
> interrupt problem to the list. I've been working on it; but if we can't
> make it work in time, maybe one option is to disable Windows
> target-async for GDB 13. I think this would probably be ok, because
> AFAIK the only thing really relying on target-async is DAP, which isn't
> going into GDB 13 anyway.
No problem, Tom.
What do you think of the following approach? Disable Windows target-async
for now, until you have a fix. That way, when I branch, it's all set,
and I can follow the standard procedure for generating the first
pre-release. Then, when we have the fix for the interrupt issue, we can
re-enable it, with the option of backporting it to the GDB 13 branch
if OK to do so.
--
Joel
next prev parent reply other threads:[~2022-12-05 3:19 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 [this message]
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
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=Y41jL16V84Ok1kx3@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).