From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: wait_reading_process_ouput hangs in certain cases (w/ patches) Date: Thu, 16 Nov 2017 17:37:20 +0200 Message-ID: <83wp2qi6a7.fsf@gnu.org> References: <83lgjz8eiy.fsf@gnu.org> <831slp98ut.fsf@gnu.org> <83tvyj62qg.fsf@gnu.org> <83r2tetf90.fsf@gnu.org> <5150d198-8dd3-9cf4-5914-b7e945294452@binary-island.eu> <83tvy7s6wi.fsf@gnu.org> <83inemrqid.fsf@gnu.org> <398f8d17-b727-d5d6-4a31-772448c7ca0d@binary-island.eu> <56e722a6-95a4-0e42-185c-f26845d4f4bf@binary-island.eu> <21237e45-a353-92f9-01ec-7b51640d2031@cs.ucla.edu> <83vaickfu2.fsf@gnu.org> <83tvxwkexg.fsf@gnu.org> <03261534-6bf5-1a5d-915f-d3c55aaa35e9@binary-island.eu> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1510846641 18239 195.159.176.226 (16 Nov 2017 15:37:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 16 Nov 2017 15:37:21 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: Matthias Dahl Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 16 16:37:14 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eFME5-0003zr-P0 for ged-emacs-devel@m.gmane.org; Thu, 16 Nov 2017 16:37:13 +0100 Original-Received: from localhost ([::1]:41437 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFME8-0002kK-Bd for ged-emacs-devel@m.gmane.org; Thu, 16 Nov 2017 10:37:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFME1-0002ha-0c for emacs-devel@gnu.org; Thu, 16 Nov 2017 10:37:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eFMDx-00046U-Tw for emacs-devel@gnu.org; Thu, 16 Nov 2017 10:37:09 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53725) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFMDx-00045k-Pv; Thu, 16 Nov 2017 10:37:05 -0500 Original-Received: from [176.228.60.248] (port=1841 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eFMDx-0001wU-7G; Thu, 16 Nov 2017 10:37:05 -0500 In-reply-to: <03261534-6bf5-1a5d-915f-d3c55aaa35e9@binary-island.eu> (message from Matthias Dahl on Wed, 15 Nov 2017 15:03:27 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:220221 Archived-At: > Cc: emacs-devel@gnu.org > From: Matthias Dahl > Date: Wed, 15 Nov 2017 15:03:27 +0100 > > The crucial part is: ALL data has been read from our wait_proc while we > were running timers or filters -- and no further data will become > available until there is some interaction again with the process. That > is the case with the ispell process. > > wait_reading_... currently has no chance/code to detect such an event > since it solely relies on pselect calls and such -- which will come up > empty handed if no further data is available, and there is nothing to > change that. Indeed, that was also my conclusion. Paul, if you are saying that there is some machinery in wait_reading_process_output to handle such situations, and it just doesn't DTRT in this case for some reason, then please point out where that code lives. Thanks.