This is the mail archive of the
mailing list for the Cygwin project.
Re: bug in execl
- To: Jason Moxham <jlm at maths dot soton dot ac dot uk>
- Subject: Re: bug in execl
- From: Chris Faylor <cygwin at sourceware dot cygnus dot com>
- Date: Wed, 19 Jan 2000 11:01:55 -0500
- Cc: cygwin at sourceware dot cygnus dot com
- References: <200001191222.MAA06611@malus.soton.ac.uk>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Wed, Jan 19, 2000 at 12:22:13PM +0000, Jason Moxham wrote:
> Bug in execl()
> Under B20.1+gcc-2.95.2 running on NT/98 under a "dos" window (not bash)
> prog1.exe consists of
> //some stuff
> return 0;}
> prog2.exe consists of
> // stuff
> return 0;}
> I pretty sure the details of the program don't matter
> No problem running it , however using task manager on NT we see that
> when prog2.exe is running , prog1.exe is still there when it should be
> overwriten .
> So a series of execl calls could easily fill up all memory , when the
> only memory required is for the program currently executing
Sorry. That's the best we can do when emulating exec on Windows.
If you run this under bash or sh you should note that this behavior does
Want to unsubscribe from this list?
Send a message to email@example.com