This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5


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 <eliz@gnu.org> wrote:
>> Date: Wed, 25 Nov 2015 12:37:15 +0100
>> From: Dominique de Waleffe <ddewaleffe@gmail.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
>
> 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]