From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: Re: `print' does not print Date: Mon, 25 Mar 2002 08:02:35 +0200 (IST) Sender: bug-gnu-emacs-admin@gnu.org Message-ID: References: <15518.13685.866557.429681@jupiter.akutech-local.de> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1017036375 29846 127.0.0.1 (25 Mar 2002 06:06:15 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 25 Mar 2002 06:06:15 +0000 (UTC) Cc: rms@gnu.org, bug-gnu-emacs@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16pNcV-0007lG-00 for ; Mon, 25 Mar 2002 07:06:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pNcT-0005NJ-00; Mon, 25 Mar 2002 01:06:13 -0500 Original-Received: from is.elta.co.il ([199.203.121.2]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pNa1-00057M-00; Mon, 25 Mar 2002 01:03:42 -0500 Original-Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id IAA12020; Mon, 25 Mar 2002 08:02:35 +0200 (IST) X-Sender: eliz@is Original-To: Ralf Fassel In-Reply-To: <15518.13685.866557.429681@jupiter.akutech-local.de> Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:139 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:139 On Sun, 24 Mar 2002, Ralf Fassel wrote: > * Eli Zaretskii > | Could you see if this change is related to the problem? For example, > | what happens if you use unexelf.c from v21.1 with an otherwise > | unmodified Emacs 21.2? > > Ok, we're getting closer. Yes; the question is how to investigate this further without having access to library sources. Hmm... Assuming for a moment that the problem is caused by some disruption of memory allocation for the standard handles, one thing to try is to use setvbuf to allocate a buffer for stdout, somewhere near the beginning of `main'. Does that help?