From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: process output has become a bit random... Date: 29 Jul 2004 08:14:01 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1091081676 29950 80.91.224.253 (29 Jul 2004 06:14:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 29 Jul 2004 06:14:36 +0000 (UTC) Cc: Peter Heslin , emacs-devel@gnu.org, handa@m17n.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 29 08:14:26 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Bq4BO-0001MJ-00 for ; Thu, 29 Jul 2004 08:14:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bq4EZ-0006lI-C8 for ged-emacs-devel@m.gmane.org; Thu, 29 Jul 2004 02:17:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bq4ET-0006lD-Ss for emacs-devel@gnu.org; Thu, 29 Jul 2004 02:17:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bq4ET-0006l1-D4 for emacs-devel@gnu.org; Thu, 29 Jul 2004 02:17:37 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bq4ET-0006ky-9O for emacs-devel@gnu.org; Thu, 29 Jul 2004 02:17:37 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bq4B2-00076N-9E for emacs-devel@gnu.org; Thu, 29 Jul 2004 02:14:04 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1Bq4B1-0007Kc-8T; Thu, 29 Jul 2004 02:14:03 -0400 Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: Original-Lines: 44 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 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 Xref: main.gmane.org gmane.emacs.devel:26078 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:26078 storm@cua.dk (Kim F. Storm) writes: > Peter Heslin writes: > > > On 2004-07-28, David Kastrup wrote: > > > Has anybody else experienced anything weird in connection with process > > > output recently? > > > > When running M-x grep recently, I got the output duplicated > > several times, which happened on a couple of random occasions. At > > the time I thought it might have been related to the super-slow > > grep output bug, but it sounds pretty close to what you describe. > > I made a change on 2004-06-07 which increased the read buffer from > 1k to 4k. I don't see how that could provoke duplicate buffer > output, though. Well, something's rotten in the state of Denmark, anyway. If you take a look at the buffer sizes, you'll see that chars is allocated with a size of carryover+readmax, but it is only ever filled with carryover old and (readmax-carryover) new characters, for a total of merely readmax characters. Consequently, I had at one time patched down either the buffer size or increased the read sizes (don't remember which it was), but that was later found to cause segmentation faults. So the change was reverted, but never explained. I have no clue whether this might be related. > Another change which may be relevant is this > > 2004-06-11 Kenichi Handa > > * coding.c (decode_coding_string): Check CODING_FINISH_INTERRUPT. > > Process output handling calls decode_coding_string in such a way that > it may not decode an entire string (leaving further decoding to the > next call). If there is some error in that logic, I think text could > be duplicated. That's a possibility, yes. Another remote one is that it may coincide with myself changing from gcc-3.3.x to gcc-3.4.1. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum