Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: Chris Faylor <cgf@cygnus.com>
Date: Thu, 21 Oct 1999 21:48:19 -0400
To: Steve Jorgensen <steve@khoral.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Wierd perl problem..
Message-ID: <19991021214818.B6885@cygnus.com>
Reply-To: cygwin@sourceware.cygnus.com
Mail-Followup-To: Steve Jorgensen <steve@khoral.com>,
	cygwin@sourceware.cygnus.com
References: <199910212318.RAA03227@benson>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <199910212318.RAA03227@benson>; from Steve Jorgensen on Thu, Oct 21, 1999 at 05:18:29PM -0600

I'm sorry.  There is a problem with using dll's after a fork with perl.
That's what you're seeing.

There is no workaround.  I hope to fix this in the next couple of months.

cgf

On Thu, Oct 21, 1999 at 05:18:29PM -0600, Steve Jorgensen wrote:
>	I'm having a really strange perl problem under cygwin 1.0
>
>	One perl script produces the following output:
>
>   0	0 [main] d:\Cygwin\contrib\bin\perl.exe 1114 fork_copy: loaded dll data/bss pass 0 failed, 0x14043000..0x1404300C, done 0, Win32 error 487
>
>	and then hangs that shell window half the time.
>
>	This happens when the perl script is executing the following line
>	of code:
>
>chop($LOCALHOST = `hostname`);
>
>	hostname is in the path, and works fine.  
>
>	This only seems to happen if the script has a
>use FileHandle;
>	line after the initialization stuff I describe above,
>	another script with the exact same initialization section
>	as the one described above works fine.  
>
>	Is there something I need to do to get the FileHandle
>	stuff working under cygwin, or am I just out of luck?

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com