X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=iu 7Q1EPBZZd2hQKOblBDjhIF2akBYIrG8at0qAV8VK8mELQI/ilY6oLUIfjGOzLb2h UTezZMSDOcxXKyL0MzTpXMYhYbraVftPmuJFPgJoi3LJoB1qlO5N40IHY6bM7qrs 1W1f9h0ZvSsCClbQltFsdBhjz6R3y/0y8pbzFOBrk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=cug1ZA7t TNUUqE6xKp8cCDXMBKU=; b=wvmfVzBIVOppp7F59mJy91+/bP+vCIDfHZNnfcmk eqFGMEvhyhUILA5M/8GRLEvee3YVynMn9o+J+BgEmRHT0s2Erkte6vhziy6gtORB sC2tlgWmEj8hGbfYnqQldeKowhHOY/B0E/21OLXbom8AfGqji5iKlPd6W8e7bfzx yDc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-lf0-f50.google.com MIME-Version: 1.0 X-Received: by 10.25.153.146 with SMTP id b140mr17642859lfe.33.1448531376807; Thu, 26 Nov 2015 01:49:36 -0800 (PST) In-Reply-To: <834mgax9lj.fsf@gnu.org> References: <834mgax9lj DOT fsf AT gnu DOT org> Date: Thu, 26 Nov 2015 10:49:36 +0100 Message-ID: Subject: Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5 From: Dominique de Waleffe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Before upgrading another machine (still on win7/64), I updated cygwin64 on it and pulled fsfemacs 24.5 (the existing binary on gnu's site) on it... Did the same test there and on win7 it works. Could this be a Windows 10 related issue? D. PS: I'll stop cc'ing the emacs list after this message as I also think it is more likely a cygwin issue. ############################ # Dominique de Waleffe # ddewaleffe -at- gmail -dot- com ############################ On Wed, Nov 25, 2015 at 6:38 PM, Eli Zaretskii wrote: >> Date: Wed, 25 Nov 2015 12:37:15 +0100 >> From: Dominique de Waleffe >> >> bash: cannot set terminal process group (-1): Inappropriate ioctl for device >> bash: no job control in this shell >> 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked >> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000, >> (child has 0x400000 - 0x600000), Win32 error 487 >> 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack trace >> to bash.exe.stackdump >> 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly, >> retry 0, exit code 0x100, errno 11 >> bash: fork: retry: No child processes >> 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked >> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000, >> (child has 0x400000 - 0x600000), Win32 error 487 >> 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack >> trace to bash.exe.stackdump >> 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died >> unexpectedly, retry 0, exit code 0x100, errno 11 > > These are Cygwin errors, which I hope Cygwin folks will be able to > interpret. Perhaps the stack dump trace produced by this will help > them even more, so I suggest to post its contents. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple