From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68274 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.gnus.general Subject: Re: (file-error "writing to process" "bad address" #) when Gcc-ing a group Date: Tue, 10 Feb 2009 16:26:19 +0100 Message-ID: <87y6we71pg.fsf@thinkpad.tsdh.de> References: <873aenr2gk.fsf@thinkpad.tsdh.de> <87tz73plyd.fsf@thinkpad.tsdh.de> <87ab8v7651.fsf@thinkpad.tsdh.de> <87y6wf43fr.fsf@randomsample.de> <87fxim8wi9.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1234279620 23559 80.91.229.12 (10 Feb 2009 15:27:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Feb 2009 15:27:00 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16714@lists.math.uh.edu Tue Feb 10 16:28:16 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LWuWz-0008RG-6K for ding-account@gmane.org; Tue, 10 Feb 2009 16:28:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LWuVG-0002K5-5e; Tue, 10 Feb 2009 09:26:26 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LWuVE-0002Jp-SN for ding@lists.math.uh.edu; Tue, 10 Feb 2009 09:26:24 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LWuVB-0006eD-NL for ding@lists.math.uh.edu; Tue, 10 Feb 2009 09:26:24 -0600 Original-Received: from deliver.uni-koblenz.de ([141.26.64.15]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LWuVV-0000x2-00 for ; Tue, 10 Feb 2009 16:26:41 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by deliver.uni-koblenz.de (Postfix) with ESMTP id 7BE4D789B16C for ; Tue, 10 Feb 2009 16:26:20 +0100 (CET) Original-Received: from deliver.uni-koblenz.de ([127.0.0.1]) by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05503-07 for ; Tue, 10 Feb 2009 16:26:19 +0100 (CET) X-CHKRCPT: Envelopesender vrfy tassilo@member.fsf.org Original-Received: from thinkpad.tsdh.de (dhcp37.uni-koblenz.de [141.26.71.37]) by deliver.uni-koblenz.de (Postfix) with ESMTP id 5C77F789B127 for ; Tue, 10 Feb 2009 16:26:19 +0100 (CET) Mail-Copies-To: never Mail-Followup-To: ding@gnus.org In-Reply-To: (David Engster's message of "Tue, 10 Feb 2009 14:51:14 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux) X-Virus-Scanned: amavisd-new at uni-koblenz.de X-Spam-Score: -5.6 (-----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68274 Archived-At: David Engster writes: > Well, color me surprised. I was just able to provoke the error with > the procedure you suggested: > > (setq numlines 500000) > > (progn > (setq proctest > (start-process "cat" (get-buffer-create "cat") "/bin/cat")) > (with-temp-buffer > (dotimes (dummy numlines) > (insert > (concat (number-to-string (random)) > (number-to-string (random)) > (number-to-string (random)) > (number-to-string (random)) > "\n"))) > (process-send-region proctest (point-min) (point-max))) > (delete-process proctest)) > > And sometimes(!) I get: > > Debugger entered--Lisp error: (file-error "writing to process" "bad address" #) > process-send-region(# 1 18672117) > > using Emacs from CVS (2009-02-04) on Darwin/Mac OS X. > > The error doesn't always happen. I usually have to repeat the > procedure several times until it occurs. You can increase 'numlines' > to make it more likely. It might also be that it depends on the load > of the system or something like that. I tried 4 times (using emacs -Q) and always (!) got the error after some seconds. System load is low. GNU Emacs 23.0.90.1 (x86_64-pc-linux-gnu, GTK+ Version 2.14.7) of 2009-02-10 on thinkpad > Maybe this > > http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=471 > > might also be connected to this issue. Yes, at least it sounds quite similar. Should I report an emacs bug report for this or do you want to do it? Bye, Tassilo