This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: SUMMARY: Known issues with gnuwin32 development tools of year 1999
- To: Chris Faylor <cgf at cygnus dot com>
- Subject: Re: SUMMARY: Known issues with gnuwin32 development tools of year 1999
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Tue, 21 Dec 1999 18:44:47 -0600 (CST)
- cc: cygwin at sourceware dot cygnus dot com
On Tue, 21 Dec 1999, Chris Faylor wrote:
> Actually, it might be but I don't really know. The specific problem
> manifests during fork. Since fork overwrites the heap, you can't
> rely on mallocing anything until after fork returns.
>
> In the case of dynamic loading we probably are ok but since this has
> bitten me once, I'm assuming that with a small tweak here or there
> it could bite us again and then we'd be scratching our heads over
> this again in a few months.
I do understand your hesitation on this.
However, fork will never work for dynamic loads -- the loading app will
get very confused at this, and I suspect the same for exec and popen as
well, so the problem is moot for dynamic loads.
My proposal still stands since it won't modify the behavior of cygwin
linked apps in any way, only change it for dynamic loads.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com