From: Dominique de Waleffe <ddewaleffe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5
Date: Thu, 26 Nov 2015 10:24:00 -0000 [thread overview]
Message-ID: <CAJVzMuUcE+rGhORZcq7t2WKvR+rK8tjby6k=R5sPp=PP+70SjA@mail.gmail.com> (raw)
In-Reply-To: <834mgax9lj.fsf@gnu.org>
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
next prev parent reply other threads:[~2015-11-26 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJVzMuVd_ijXXmYJe+BXszroW0pZExA_mOCH-vwoeUhgpd+22g@mail.gmail.com>
2015-11-25 18:22 ` Eli Zaretskii
2015-11-26 10:24 ` Dominique de Waleffe [this message]
2015-11-26 14:19 ` Corinna Vinschen
2015-11-26 18:00 ` Dominique de Waleffe
2015-11-26 18:00 ` Achim Gratz
2015-11-26 19:43 ` Dominique de Waleffe
2015-11-26 21:32 ` Dominique de Waleffe
2015-11-27 9:00 ` Eli Zaretskii
2015-11-27 9:30 ` Dominique de Waleffe
2015-11-27 14:51 ` Eli Zaretskii
2015-12-02 16:32 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJVzMuUcE+rGhORZcq7t2WKvR+rK8tjby6k=R5sPp=PP+70SjA@mail.gmail.com' \
--to=ddewaleffe@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).