From: Maxime Devos <maximedevos@telenet.be>
To: Andrew Tropin <andrew@trop.in>, guile-devel@gnu.org
Cc: Andy Wingo <wingo@igalia.com>, 48566@gnu.org
Subject: Re: [BUG] Non-local exit in thunk from system-async-mark doesn't restore asyncs block
Date: Wed, 11 Oct 2023 00:22:38 +0200 [thread overview]
Message-ID: <1abe3408-f477-3283-6405-cc62495ffa13@telenet.be> (raw)
In-Reply-To: <871qe8fj68.fsf@trop.in>
[-- Attachment #1.1.1: Type: text/plain, Size: 715 bytes --]
Op 06-10-2023 om 06:50 schreef Andrew Tropin:
> TLDR:
> abort-to-prompt restores asyncs block level.
> abort-to-prompt from a procedure scheduled with system-async-mark
> doesn't restort asyncs block level.
Looks like a duplicate or variant of
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48566>
to me. (Maybe that's why you put me in CC?)
It has a smaller/simpler reproducer.
Don't have more information, though, beyond a guess that maybe the
blocking/unblocking is actually going well but due to continuation
shenanigans, the block level would need to (temporarily) become
negative, and libguile/asyncs.c is too strict in its checks.
Or maybe I'm confusing things with another bug ...
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2023-10-10 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 4:50 [BUG] Non-local exit in thunk from system-async-mark doesn't restore asyncs block Andrew Tropin
2023-10-10 22:22 ` Maxime Devos [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1abe3408-f477-3283-6405-cc62495ffa13@telenet.be \
--to=maximedevos@telenet.be \
--cc=48566@gnu.org \
--cc=andrew@trop.in \
--cc=guile-devel@gnu.org \
--cc=wingo@igalia.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).