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=Xm
	PfLg0ZEQLgb8Pzdn193620YUhHfHMxp/rUhdLoOwfCJb9tNkTPq0xWOJpKI5Erq7
	Bi7c50ssKsQe19VDHFOVG7+y1Itc++f2+d0n5J1SYMuHBjg0m9kM2QvLfGpxMoyk
	rV+BEOnp6AnIC9qO+wAJJPtlfD1rVjVY1l8dL9h6M=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <20151126135158.GO2755@calimero.vinschen.de>
References: <834mgax9lj DOT fsf AT gnu DOT org>	<20151126135158 DOT GO2755 AT calimero DOT vinschen DOT de>
Date: Thu, 26 Nov 2015 18:26:55 +0100
Message-ID: <CAJVzMuVgWbTer8z4xT00_Uh6asKGvLVqrm2W2cK_6pDUMxJgLg@mail.gmail.com>
Subject: Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5
From: Dominique de Waleffe <ddewaleffe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: multipart/mixed; boundary=001a11406b62a595ca052574e122

--001a11406b62a595ca052574e122
Content-Type: text/plain; charset=UTF-8

Corinna,
Thanks for the pointer.

I have checked the BLODA list. The only thing I have is windows
defender (part of the os:-(
It can be disabled via  group policy. (but I am not tempted to do that
for long term)
I did that but same issue...

I have rebased the whole cygwin as suggested also.
That did not fix the problem either.

I attached the bash stack trace in case it may help.

If you have any idea as to what I could do to help debug this... I'll
be happy to help.

Meanwhile, I'll make a VM with a fresh install of Win10 (v1511 x64)
and just Emacs + cygwin and see whether there is something fishy about
my current setup after the upgrades it went through...

D.

############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Thu, Nov 26, 2015 at 2:51 PM, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> On Nov 25 19:38, Eli Zaretskii wrote:
>> > Date: Wed, 25 Nov 2015 12:37:15 +0100
>> > From: Dominique de Waleffe <ddewaleffe AT gmail DOT com>
>> >
>> > 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
>
> https://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures
>
>> 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.
>
> So it looks like this is either a BLODA(*) problem, or rebasing the
> entire distro is necessary(**).
>
>
> Corinna
>
>
> (*)  https://cygwin.com/faq/faq.html#faq.using.bloda
> (**) https://cygwin.com/ml/cygwin-announce/2015-02/msg00014.html
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat

--001a11406b62a595ca052574e122
Content-Type: application/octet-stream; name="bash.exe.stackdump"
Content-Disposition: attachment; filename="bash.exe.stackdump"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_ihghln4e1

U3RhY2sgdHJhY2U6DQpGcmFtZSAgICAgICAgRnVuY3Rpb24gICAgQXJncw0K
MDAwMDAwMDAwMDAgIDAwMTgwMDcxRjhFICgwMDE4MDIxMkZEQywgMDAxODAy
MTJFODYsIDAwMDAwNDAwMDAwLCAwMDAwMDVGRUUxMCkNCjAwMDAwMDAwMDAw
ICAwMDE4MDA0NkUyMiAoMDAwMDA1RkZFNzgsIDAwMDAwMDAwMDAwLCAwMDAw
MDAwMDAwMCwgMDAwMDAwMDIwMDApDQowMDAwMDAwMDAwMCAgMDAxODAwNDZF
NjIgKDAwMDAwNjAwMDAwLCAwMDAwMDgwMDAwMCwgMDAwMDA0MDAwMDAsIDAw
MDAwNjAwMDAwKQ0KMDAwMDAwMDAwMDAgIDAwMTgwMDQ3MTYxICgwMDAwMDAw
MDAwMCwgMDAxMDA0MDEwMDAsIDAwMDAwMjg0MDAwLCAwMDAwMDAwMDAwMCkN
CjAwMDAwMDAwMDAwICAwMDE4MDA0NzFBRSAoMDAwMDAwMDAwMDAsIDAwMDAw
MDAwMDAwLCAwMDAwMDAwMDAwMCwgMDAwMDAwMDAwMDApDQowMDAwMDAwMDAw
MCAgMDAxMDA0NzJERDEgKDAwMDAwMDAwMDAwLCAwMDAwMDAwMDAwMCwgMDAw
MDAwMDAwMDAsIDAwMDAwMDAwMDAwKQ0KMDAwMDAwMDAwMDAgIDAwMTAwNDAx
MDEwICgwMDAwMDAwMDAwMCwgMDAwMDAwMDAwMDAsIDAwMDAwMDAwMDAwLCAw
MDEwMDQwMTAwMCkNCjAwMDAwMDAwMDAwICA3RkY4RTAyMTgxMDIgKDAwMDAw
MDAwMDAwLCAwMDAwMDAwMDAwMCwgMDAwMDAwMDAwMDAsIDAwMDAwMDAwMDAw
KQ0KMDAwMDAwMDAwMDAgIDdGRjhFMTJGQzI2NCAoMDAwMDAwMDAwMDAsIDAw
MDAwMDAwMDAwLCAwMDAwMDAwMDAwMCwgMDAwMDAwMDAwMDApDQpFbmQgb2Yg
c3RhY2sgdHJhY2UK


--001a11406b62a595ca052574e122
Content-Type: text/plain; charset=us-ascii

--
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
--001a11406b62a595ca052574e122--