Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sun, 9 Sep 2001 20:57:31 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: fixup_after_fork_not?
Message-ID: <20010909205731.A26374@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F140 AT itdomain002 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F140@itdomain002.itdomain.net.au>
User-Agent: Mutt/1.3.21i

On Mon, Sep 10, 2001 at 10:31:52AM +1000, Robert Collins wrote:
>
>
>> -----Original Message-----
>> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
>> 
>> I'm pretty sure that the fork fixup routines are running.  If 
>> they weren't
>> then fork wouldn't be operational.
>
>sure :]. Its the only-shows-output-when-exec-occurs-from-tcsh that has
>me intrigued.
> 
>> You do have to make sure that you call anything which uses 
>> malloc at the
>> proper point or some things (like mutos) won't be properly 
>> initialized.
>
>does system_printf use malloc? Otherwise what I'm doing is pretty basic.
>(win32 CreateMutex call and a list iteration.).
>
>> I've just reduced the size of the problematic 'zombies' 
>> array.  I don't know
>> if that is what is causing your size problems but it should 
>> make the DLL
>> noticeably smaller.
>
>Thanks. When I get home I'll give feedback.
> 
>> If you can't, for some reason, debug a DLL that is entirely 
>> built with -g,
>> try compiling everything except fork.cc and thread.c (or 
>> whatever) with '-O2'
>> and those to files with '-g'.
>> 
>> You are using the latest version of binutils, right?
>
>No, I'm still using the cross-compile toolkit I setup a while back. Do I
>need to update that for correct functionality?

Hmm.  No.  I don't see why you would.

Actually, I don't see why I even asked the question.  :-)  It should work
fine with any relatively "modern" binutils.

cgf