X-Authentication-Warning: new-smtp2.ihug.com.au: Host p185-tnt4.syd.ihug.com.au [203.173.134.185] claimed to be acceleron Message-ID: <021701c12e20$36865910$0a02a8c0@acceleron> From: "Andrew Cottrell" To: , "Mark E." References: <3B878FB3 DOT 2670 DOT 118B0A AT localhost> Subject: Re: Bash 2.05 beta 23-Aug-2001 with Win 2K Date: Sun, 26 Aug 2001 21:14:00 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Reply-To: djgpp-workers AT delorie DOT com ----- Original Message ----- From: "Mark E." To: Sent: Sunday, August 26, 2001 1:44 AM Subject: Re: Bash 2.05 beta 23-Aug-2001 with Win 2K > > an update from the 23-Aug-2001 which I downloaded and compiled. There are > > some very interesting memory corruption quirks I have found. These are > > bizare to say the least. > > This update disabled Bash's selector leak solution so it wouldn't get in the > way of libc's. I've updated bash again to fix an off-by-one error. I've also > added ARRAY_INIT_LEN so you can turn it up to a value that will let you get > by if the problem still isn't fixed. > > http://snowballville.tripod.com/djgpp/ > Mark, Just got a few minutes to rebuild Bash from the updated sources and this is what I found: ARRAY_INIT_LEN Outcome 32 Crashes as before 64 Crashes as before 80 Started to configure grep 92 Started to configure grep 128 Started to configure grep 256 Started to configure grep Configuring Grep exists with a configuration issuem, rather than a crash as outlined in the table above. The exit is: checking for mingw32 environment... no checking for DJGPP environment... yes checking for environ variable separator... ; checking for executable suffix... configure: error: installation or configuration problem: compiler cannot create executables. I stil need to do the following: 1) See if I can use gdb to debug the app before it crashes to find out where the memory corruption occurs. This assumes that the corruption still occurs if I run Bash from GDB. 2) Go over the config.log file when I have some more time later, probably one night during the week. This will propbably take me at least a 3 days to do. Andrew