Date: Sun, 26 Aug 2001 16:18:41 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andrew Cottrell <acottrel AT ihug DOT com DOT au>
cc: djgpp-workers AT delorie DOT com, "Mark E." <snowball3 AT bigfoot DOT com>
Subject: Re: Bash 2.05 beta 23-Aug-2001 with Win 2K
In-Reply-To: <021701c12e20$36865910$0a02a8c0@acceleron>
Message-ID: <Pine.SUN.3.91.1010826161345.7088C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sun, 26 Aug 2001, Andrew Cottrell wrote:

> ARRAY_INIT_LEN        Outcome
>      32                                Crashes as before
>      64                                Crashes as before
>      80                               Started to configure grep

Is the value of ARRAY_INIT_LEN used to allocate some specific array, or a 
small number of arrays?  If so, you could put a watchpoint just beyond 
the end of an allocated array, and see if some code overruns it.

If it's possible that these arrays are passed to free without being the 
result of malloc, putting a watchpoint that watches the 4 bytes 
immediately preceding the array beginning might find the offending code.

If there are more than one array, you will have to try that with each 
one of them in turn...

> checking for DJGPP environment... yes
> checking for environ variable separator... ;
> checking for executable suffix... configure: error: installation or
> configuration problem: compiler cannot create executables.

That's strange: it identified the DJGPP environment correctly, but claims 
that compiling a program fails.  What does config.log say about this?