X-Authentication-Warning: smtp3.ihug.com.au: Host p84-tnt1.syd.ihug.com.au [203.173.128.84] claimed to be acceleron Message-ID: <002501c11be1$45e06550$0a02a8c0@acceleron> From: "Andrew Cottrell" To: Cc: , References: Subject: Re: Make 3.791 on Windows 2000 test Date: Fri, 3 Aug 2001 15:58:07 +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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Reply-To: djgpp-workers AT delorie DOT com Eli & Charles, > > > So do I understand correctly that Make, either rebuilt with the Unixy > > > sbrk flag set in its main function, or linked with hacked up crt1.c which > > > makes Unixy sbrk the default, does not crash? And that cc1.exe, even > > > after rebuilding it, still crashes with the same traceback which shows > > > address wrap-around? > > I think you are correct in spotting Make does not crash with the Unixy sbrk > > flag set. Let me run a series of tests again with the following combination, > > this may take a few days: > > 1) Make & GCC - no Unixy SBRK, no malloc_debug > > 2) Make & GCC - no Unixy SBRK, malloc_debug set to 4 for both > > 3) Make & GCC - Unixy SBRK set, no malloc_debug > > 4) Make & GCC - Unixy SBRK set, malloc_debug set to 4 for make only > > 5) Make & GCC - Unixy SBRK set, malloc_debug set to 4 for both make and GCC > > Are there any other combinatios that would help give more info? > > I don't think we need more at this time. In fact, I'd even say forget > the malloc_debug version and run only the normal combinations, with and > without Unixy sbrk. A combination where Make is with Unixy sbrk but GCC > isn't might also be useful. > Should I still go ahead with this or just try Charles's Windows 2000/sbrk source patch and see what occurs? The patch only appears to work on the standard DJ203 binaries from Simtel, not the ones I have built using the CVS tarball. So I will need to rebuild DJGPP, GCC and Make to re-test with the patch as the DJ203 binaries don't set the DJDEV environment variable without the FAT32 changes.