From: "Mark E." To: djgpp-workers AT delorie DOT com Date: Fri, 18 May 2001 21:53:45 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Possible bash issue Message-ID: <3B0599E9.21329.13FC05@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > So is this likely to be a bug in bash, or a libc problem (my > bash is linked against stock 2.03)? I made the example stand-alone (by providing a script that performs the same function as --fallback-echo) and I couldn't reproduce the problem. I changed to a previous bash 2.04 and also got the same answer. bash 2.05 also gives the same answer. I added a statement to output the i variable and it stops at 16 every time (2.04 current, 2.04 previous, 2.05 alpha). I also manually ran 'ltconfig ltmain.sh' and it gave the same answer. You might try disabling the memory leak fix in execute_cmd.c (search for 'free (args)') and see if that makes a difference. Mark