From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: GDB 10.1 release -- 2020-09-18 Update
Date: Wed, 23 Sep 2020 10:00:58 -0400 [thread overview]
Message-ID: <a3cb49d9-1e43-07fe-44f9-b64431334855@simark.ca> (raw)
In-Reply-To: <87k0wkpq82.fsf@tromey.com>
On 2020-09-23 9:39 a.m., Tom Tromey wrote:
> Simon> Here's another regression since the last release, which should be
> Simon> fixed prior to the release:
>
> Simon> "maintenance set target-async off" is broken on GNU/Linux
> Simon> https://sourceware.org/bugzilla/show_bug.cgi?id=26642
>
> Is there some particular need for this?
> I tend to think maintenance commands shouldn't block a release.
>
> Tom
There is no real need for using "target-async off" on Linux, but I think
it exposes a real bug in the core of GDB (in infrun) that would affect
any sync target.
However, the bug happens because even in target-async off mode,
linux_nat_target::wait obeys the TARGET_WNOHANG and doesn't block.
Maybe that doesn't make sense: a sync target should block in wait, by
definition. Any other sync target would just ignore TARGET_WNOHANG, so
we wouldn't hit the same bug as I hit with the linux-nat target.
Simon
prev parent reply other threads:[~2020-09-23 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 23:46 Joel Brobecker
2020-09-19 1:37 ` Simon Marchi
2020-09-19 19:42 ` Joel Brobecker
2020-09-19 23:58 ` Simon Marchi
2020-09-19 7:41 ` Eli Zaretskii
2020-09-19 19:48 ` Joel Brobecker
2020-09-21 16:26 ` Eli Zaretskii
2020-09-26 17:39 ` Joel Brobecker
2020-09-28 9:30 ` Eli Zaretskii
2020-09-28 20:11 ` Joel Brobecker
2020-10-09 19:53 ` [pushed/gdb-10-branch] gnulib: fix stat/fstat build errors on old Windows version or using old MinGW Joel Brobecker
2020-09-20 1:03 ` GDB 10.1 release -- 2020-09-18 Update Simon Marchi
2020-09-20 6:09 ` Eli Zaretskii
2020-09-21 19:54 ` Simon Marchi
2020-09-23 13:39 ` Tom Tromey
2020-09-23 14:00 ` Simon Marchi [this message]
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=a3cb49d9-1e43-07fe-44f9-b64431334855@simark.ca \
--to=simark@simark.ca \
--cc=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).