Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm 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: Jason Moxham Message-Id: <200001191222.MAA06611@malus.soton.ac.uk> Subject: bug in execl To: cygwin AT sourceware DOT cygnus DOT com Date: Wed, 19 Jan 2000 12:22:13 +0000 (GMT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bug in execl() --------------- Under B20.1+gcc-2.95.2 running on NT/98 under a "dos" window (not bash) prog1.exe consists of {signal(SIGHUP,SIG_IGN); //some stuff execl("prog2.exe","prog2.exe",argv[1],argv[2],argv[3],0); return 0;} prog2.exe consists of {signal(SIGHUP,SIG_IGN); // 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 Thanks Jason Moxham jlm AT maths DOT soton DOT ac DOT uk -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com