Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 26 Oct 1999 21:45:16 -0400 To: Steve Jorgensen Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Wierd perl problem.. Message-ID: <19991026214516.A3136@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Steve Jorgensen , cygwin AT sourceware DOT cygnus DOT com References: <199910262153 DOT PAA09692 AT benson> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199910262153.PAA09692@benson>; from Steve Jorgensen on Tue, Oct 26, 1999 at 03:53:12PM -0600 On Tue, Oct 26, 1999 at 03:53:12PM -0600, Steve Jorgensen wrote: >> > Ok. I've just checked in changes that work around the problem "for me". >> > They should be in the next snapshot. > >> > The problem was that a DLL in a forked child was not being loaded in >> > exactly the same location as it was in the parent. So, when the parent >> > tried to copy its memory to the child -- boom! > >> > I kludged around this by allocating memory up to the point where the >> > DLL should be loaded. This is remarkably fragile and stupid but it >> > seems to work. > >> > The DLL code looks like it is due for a rewrite. Maybe we'll have time >> > to do that someday. > >> > So, if you're adventurous, try out the latest snapshot and see if dynamic >> > loading in perl just miraculously "works" now. > >> I'll play with it. Thanks. > > Just tried the October 10, 1999 snapshot cygwin1.dll, and the > perl problem is fixed.. Thanks! Um. The October 10 snapshot should not have fixed anything. I only worked on the problem last weekend. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com