Date: Wed, 1 Aug 2001 13:59:44 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Andrew Cottrell cc: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com Subject: Re: Make 3.791 on Windows 2000 test In-Reply-To: <000901c11a76$14551d30$0a02a8c0@acceleron> Message-ID: 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 Wed, 1 Aug 2001, Andrew Cottrell wrote: > > 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. > DJGPP_204 D:\dj204\lib\gcc-lib\djgpp\2.953>gdb cc1.exe > ....CUT GNU gdb 5.0 info... > (gdb) break main > Breakpoint 1 at 0xc4e5 > (gdb) run > Starting program: d:/dj204/lib/gcc-lib/djgpp/2.953/cc1.exe > > Breakpoint 1, 0xc4e5 in main () > (gdb) print _crt0_startup_flags > $1 = 2048 > (gdb) > > > Also, please make sure that the cc1.exe binary which gets run and crashes > > when you try to rebuild Make is the same binary you built with the > > hacked up version of crt1.c. (Sorry for asking the obvious ;-) > It's the only one that is on the DJGPP directory on the Windows 2000 PC. Didn't you say that you have 2 DJGPP installations there? Is it true that your DJGPP environment variable is set to D:\dj204\djgpp.env, and that there's no cc1.exe in D:\dj204\bin? In any case, the traceback shows explicitly what binary was running, including its full path; please double-check that when you run your tests. Thanks again for working on this.