public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fork problem on latest cygwin CVS
Date: Tue, 15 Nov 2011 19:22:00 -0000	[thread overview]
Message-ID: <20111115192202.GB18893@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4EC27F70.60102@gmail.com>

On Tue, Nov 15, 2011 at 04:04:16PM +0100, marco atzeri wrote:
>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

Amazingly short.  Thanks very much!  I can duplicate this and will fix it.

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

  reply	other threads:[~2011-11-15 19:22 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
2011-11-15 19:22         ` Christopher Faylor [this message]
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=20111115192202.GB18893@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).