Mail Archives: cygwin/1999/10/26/17:55:49
> > 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!
Steve
--
-----------------------------------------------------------
Steven Jorgensen steve AT khoral DOT com steve AT haunt DOT com
------------------------------+----------------------------
Khoral Research Inc. | PHONE: (505) 837-6500
6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842
Albuquerque, NM 87110 | URL: http://www.khoral.com/
-----------------------------------------------------------
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -