Mail Archives: djgpp-workers/2001/08/03/02:03:27
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.
- Raw text -