From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fork problem on latest cygwin CVS
Date: Mon, 14 Nov 2011 17:11:00 -0000 [thread overview]
Message-ID: <20111114171105.GA22991@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4EC13D23.8040705@gmail.com>
On Mon, Nov 14, 2011 at 05:09:07PM +0100, marco atzeri wrote:
>On 11/14/2011 4:31 PM, Christopher Faylor wrote:
>> On Mon, Nov 14, 2011 at 03:40:32PM +0100, marco atzeri wrote:
>>> Hi Cgf,
>>>
>>>
>>> after updating cygwin CVS build from
>>> http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html
>>> to
>>> http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00064.html .. 66html
>>>
>>> on CYGWIN_NT-6.1-WOW64
>>>
>>> the shell have fork issues during make/build session.
>>
>> Come on, you know the drill by now. How about a simple test case?
>
>I know the drill, but I just updated from XP-32 to W7-64,
>one disk crashed, so I am reinstalling everything from scratch and
>taking a test case when building octave is never easy.
>
>So I need time to give you a simple test case, and eventually
>someone else will notice the same problem in advance.
>
>FYI 2011-11-08 snapshot does not suffer such problem.
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
--
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-14 17:11 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 [this message]
2011-11-15 15:05 ` marco atzeri
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=20111114171105.GA22991@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.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).