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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: fixup_after_fork_not?
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Mon, 10 Sep 2001 10:31:52 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F140@itdomain002.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: fixup_after_fork_not?
Thread-Index: AcE5jLGsAHZ2UUZmQum1pswqbqJzkQAAp7qw
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id UAA27964



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

Rob