From: David Kastrup <dak@gnu.org>
Subject: Another BLOCK_INPUT/record_unwind_protect/UNBLOCK_INPUT nesting
Date: Sat, 26 Feb 2005 16:35:00 +0100 [thread overview]
Message-ID: <x5bra7uyfv.fsf@lola.goethe.zz> (raw)
xselect.c line 752, also 1419
I am not versed enough in the matter, but since signals restore the
setting of interrupt_input_blocked, those would appear to be bugs.
They appear to me as bugs leaving the blockage count too high, so I
don't see how they could be responsible for the underrun that is
annoying me. Still...
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next reply other threads:[~2005-02-26 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 15:35 David Kastrup [this message]
2005-02-27 13:43 ` Another BLOCK_INPUT/record_unwind_protect/UNBLOCK_INPUT nesting Richard Stallman
2005-02-27 18:57 ` David Kastrup
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5bra7uyfv.fsf@lola.goethe.zz \
--to=dak@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).