Message-ID: <4AD7BAB1.5080304@gmail.com>
Date: Fri, 16 Oct 2009 01:13:37 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: fork failure?
References: <4AD732C7.4020301@cwilson.fastmail.fm> <4AD73B83.9060505@gmail.com> <4AD74586.8070803@cwilson.fastmail.fm> <4AD752C8.2040908@gmail.com> <4AD7B135.6020401@cwilson.fastmail.fm>
In-Reply-To: <4AD7B135.6020401@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Charles Wilson wrote:
> So it looks to me like something in cwdstuff::init() triggered a signal,
> which was caught by cygwin and handled by aborting.
>
> Does that analysis look right?

  It certainly does.

> [ ... ] appears that the child is dying in dcrt0.c dll_crt0_1() when it
> calls cygheap->cwd.init().  

  That so rings a bell, I'm sure I've had that happen to me or seen or read it
before somewhere.  Is that maybe where it crashed when the DLL was in the root
dir of a drive and it wasn't able to ascend up a level to find the definition
of '/' after assuming the dll had to be in '/bin'?

    cheers,
      DaveK

--
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