From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: wait_reading_process_ouput hangs in certain cases (w/ patches) Date: Mon, 26 Feb 2018 08:52:46 -0800 Message-ID: References: <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> <206ebefa-7583-f049-140c-c8fd041b0719@cs.ucla.edu> <709614e8-1937-07c1-f554-b453ed4f3d4a@binary-island.eu> <7550438b-9fd4-d374-e571-8bb16456cad5@cs.ucla.edu> <797d0e16-1bae-50c2-35f8-05489ffce935@binary-island.eu> <83tvugdiu5.fsf@gnu.org> <877er5s0xv.fsf@gmail.com> <4e4c72bb-295d-81e1-e4ed-cad256bca83c@binary-island.eu> <87zi3v9461.fsf@gmail.com> <87y3jf93bu.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1519663905 9538 195.159.176.226 (26 Feb 2018 16:51:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Feb 2018 16:51:45 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 Cc: Matthias Dahl , Eli Zaretskii , eggert@cs.ucla.edu, emacs-devel@gnu.org To: =?UTF-8?Q?andr=c3=a9s_ram=c3=adrez?= , Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 26 17:51:40 2018 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 1eqM01-000201-Tp for ged-emacs-devel@m.gmane.org; Mon, 26 Feb 2018 17:51:38 +0100 Original-Received: from localhost ([::1]:60079 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqM24-0001ep-FN for ged-emacs-devel@m.gmane.org; Mon, 26 Feb 2018 11:53:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqM1N-0001eG-Df for emacs-devel@gnu.org; Mon, 26 Feb 2018 11:53:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqM1M-0006Tk-Gv for emacs-devel@gnu.org; Mon, 26 Feb 2018 11:53:01 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:59320) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eqM1M-0006TU-7E; Mon, 26 Feb 2018 11:53:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=2v2z7bI2GCTDxKakv+ERYEEVlksb48qP6RucjTdZw5M=; b=P84etizJnl0fTC7ufR/8b83oEnqBSLRtkRpPoyJM4xUidAs/mH4rc2O4fPNtvqLz8G4YTCMOPdfFQg3lyRxmtLGKpuJpbcE3+KOLasDU3xMMnEOJ1KrzZhnyXQao+bGriY1c/bYoGq1csd5XARwVM6ieK2cbAgR/RQoaRMwDnY0KuYGCzOSpYAFkP81C3w1sZ0npgejXjenO9oqlRuv5E7+MBxvUm5xd3qZK1F5ne7q65XtMEmEhEFosLRwHBCpz0uzlwfTrVi1ObWirHuT6XcOtHAbRIu/rxmA9LO/PpflFxe0XfJ5Io5x8KXth8bzpIvqVpWNsQTPyiaYnPwRzUw==; Original-Received: from [2604:4080:1321:8ab0:2891:b7:d72c:af1b] by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1eqM1E-00014o-VX; Mon, 26 Feb 2018 08:52:53 -0800 In-Reply-To: <87y3jf93bu.fsf@gmail.com> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:223066 Archived-At: On 02/26/2018 07:29 AM, andrés ramírez wrote: >> The fixes to wait_reading_process_ouput have definitely made a >> difference. I used to see hangs several times a day, but after the fix, >> I'm only seeing the hangs once every few days, and it's impossible to >> set up a repeatable test case for them. So my guess is that there might >> still be a problem in this area, but that the window for triggering it >> is much smaller. > > Right. I was thinking the last some days about backporting this change > by myself even to emacs-23 which I still use on an embedded platform (my > phone). Why wouldn't the phone run a newer Emacs?