Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!ames!uhccux!munnari.oz.au!cluster!metro!natmlab.dap.csiro.au!ditsyda!evans
From: evans@ditsyda.oz (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: Installing PC 1.5.3
Message-ID: <2465@ditsyda.oz>
Date: 25 Feb 90 05:49:45 GMT
References: <11884@nigel.udel.EDU>
Reply-To: evans@ditsyda.oz (Bruce Evans)
Organization: CSIRO DIT Sydney, Australia
Lines: 25

In article <11884@nigel.udel.EDU> bunnell@henry.asel.udel.edu (Tim Bunnell) writes:
|	ar q libc.a 'lorder *.s | tsort'
|
|gives every appearance of actually working.  However, it reports a cycle
|between malloc and memmove (the assembly version which also contains

I saw this in 1.5.0 too. It appears to be a bug in lorder.

|but in trying to do so I noticed that malloc has DEBUG code enabled.  Is this
|the recommended setting for that routine at present?  Will anything break if
|the debugging code is disabled?

I think the routine is well enough debugged by now. I have seen the "assertion
failed" message from it a few times, but it was always from a bad argument to
free or the stack being too small. Someone should test how much time the
extra tests costs. If not much, leave the tests in, but don't call them DEBUG
code.

|commands and libraries.  Are we to rebuild the boot image and kernel using
|the old kernel + new fs-mm-tools, or wait for the new kernel before taking
|that step?

Use the old one.
-- 
Bruce Evans		evans@ditsyda.oz.au