From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: fork problem on latest cygwin CVS
Date: Tue, 15 Nov 2011 15:05:00 -0000 [thread overview]
Message-ID: <4EC27F70.60102@gmail.com> (raw)
In-Reply-To: <20111114171105.GA22991@ednor.casa.cgf.cx>
On 11/14/2011 6:11 PM, Christopher Faylor wrote:
> FYI, the last thing any developer wants to hear after a major code
> change is a generic "It's broke" report with no details and no way to
> duplicate the problem. A stack trace from a home-grown version of
> cygwin1.dll is not a detail. It's meaningless unless the addresses are
> decoded.
>
> cgf
Ok,
rewinding to step 1
I simplified the test case to a short one, involving just 1 make call,
using your snapshot
$ uname -a
CYGWIN_NT-6.1-WOW64 MARCOATZERI 1.7.10s(0.255/5/3) 20111114 02:01:52
i686 Cygwin
please find it on:
http://matzeri.altervista.org/works/test_case/
calling
make oct-conf.h
produces:
--------------------------------------------------------------------
making oct-conf.h from oct-conf.h.in
0 [main] sh 4636 E:\cygwin\bin\sh.exe: *** fatal error in forked
process - fork: can't commit memory for stack 0x28C000(81920), Win32
error 487
Stack trace:
Frame Function Args
0028EBB8 6102B30B (0028EBB8, 00000000, 00000000, 00000000)
0028EEA8 6102B30B (61192F60, 00008000, 00000000, 61194A6C)
0028FED8 61005403 (61194FB0, 0028FEF4, 0028FF08, 61006BE1)
0028FEE8 61005438 (61194FB0, 0028C000, 00014000, 00000040)
0028FF08 61006BE1 (007F102E, 0028FF10, 00001F80, 037F037F)
0028FF38 61006C2D (007F102E, 00000000, 0028FF58, 00465672)
0028FF48 61006CAB (00401F10, 00000000, 0028FF88, 00401033)
0028FF58 00465672 (00401F10, 00000000, 00000000, 00000000)
0028FF88 00401033 (7EFDE000, 0028FFD4, 770A9ED2, 7EFDE000)
0028FF94 750E33CA (7EFDE000, 7660A4F7, 00000000, 00000000)
0028FFD4 770A9ED2 (00401000, 7EFDE000, 00000000, 00000000)
0028FFEC 770A9EA5 (00401000, 7EFDE000, 00000000, 78746341)
End of stack trace
0 [main] sh 300 fork: child -1 - forked process died
unexpectedly, retry 10, exit code 256, errno 11
/bin/sh: fork: retry: Resource temporarily unavailable
...
-----------------------------------------------------------------------
this does not happen with 20111108
Regards
Marco
--
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:[~2011-11-15 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 14:40 marco atzeri
2011-11-14 15:31 ` Christopher Faylor
2011-11-14 16:09 ` marco atzeri
2011-11-14 17:11 ` Christopher Faylor
2011-11-15 15:05 ` marco atzeri [this message]
2011-11-15 19:22 ` Christopher Faylor
2011-11-16 19:14 ` Christopher Faylor
2011-11-16 22:01 ` marco atzeri
2011-11-16 22:24 ` Christopher Faylor
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=4EC27F70.60102@gmail.com \
--to=marco.atzeri@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).