From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Hendrik Tews <hendrik@askra.de>
Cc: 13400@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#13400: 23.4; overlapping process filter calls
Date: Tue, 06 Aug 2019 03:40:44 -0400 [thread overview]
Message-ID: <jwvwofqhhhy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87wofr1bog.fsf@cert.kernkonzept.com> (Hendrik Tews's message of "Tue, 06 Aug 2019 00:37:19 +0200")
> complete. If the programmer cannot rely on the documentation to
> be complete here, he or she has no other choice than to assume
> that output can arrive anywhere and he/she _is_ plagued with the
> usual parallel programming problems.
While I largely agree with your points, I'll mention that we *are*
plagued, because lots of functions may (in some cases) end up calling
a blocking operation. E.g. any call to a file function can block if the
file happens to be handled by Tramp, so any call to a function which
(transitively) calls a file function can itself block.
> It is about a few words making the documentation more precise,
> potentially saving somebody a painful debugging session of
> several hours - similar to what I went through in 2013. Back
> then, I was lucky because clearing the disk caches was enough to
> reproduce the problem. Today with SSD's it is probably much
> harder...
I think preventing recursive filter invocations (by default) would be
much better than warning the programmer about that odd possibility.
Stefan
next prev parent reply other threads:[~2019-08-06 7:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 10:11 bug#13400: 23.4; overlapping process filter calls Hendrik Tews
2019-07-27 3:38 ` Noam Postavsky
2019-07-27 8:24 ` Eli Zaretskii
2019-08-04 0:02 ` Noam Postavsky
2019-08-04 16:29 ` Eli Zaretskii
2019-08-05 18:31 ` Stefan Monnier
2019-08-08 3:37 ` Noam Postavsky
2019-08-08 13:36 ` Eli Zaretskii
2019-08-09 21:36 ` Stefan Monnier
2019-08-10 1:39 ` Noam Postavsky
2019-08-10 9:03 ` Stefan Monnier
2019-08-05 22:37 ` Hendrik Tews
2019-08-06 7:40 ` Stefan Monnier [this message]
2019-08-08 1:15 ` Noam Postavsky
2019-08-20 12:19 ` Noam Postavsky
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=jwvwofqhhhy.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=13400@debbugs.gnu.org \
--cc=hendrik@askra.de \
--cc=npostavs@gmail.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.
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).