From owner-freebsd-current  Sun Feb  9 16:20:39 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA21575
          for current-outgoing; Sun, 9 Feb 1997 16:20:39 -0800 (PST)
Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA21548
          for <current@freebsd.org>; Sun, 9 Feb 1997 16:20:28 -0800 (PST)
Received: from why.whine.com ([205.150.249.1]) by mail2.uunet.ca with ESMTP id <123109-27423>; Sun, 9 Feb 1997 19:20:26 -0500
Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id TAA20080; Sun, 9 Feb 1997 19:19:51 -0500 (EST)
Date: Sun, 9 Feb 1997 19:19:50 -0500
From: Andrew Herdman <andrew@why.whine.com>
X-Sender: andrew@why
To: Andrew Herdman <andrew@why.whine.com>
cc: Poul-Henning Kamp <phk@critter.dk.tfs.com>, current@freebsd.org
Subject: Re: Make world of Current dies with weird errors. 
In-Reply-To: <Pine.BSF.3.95.970209134139.28945A-100000@why>
Message-ID: <Pine.BSF.3.95.970209191813.20055A-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I was able to actually make world today.  I had been overclocking my cpu
at a 75mhz bus vs. a 66mhz bus.  Dropping it to 66, or disabling the
level2 cache cause the problem to go away.  Question is... why is the only
thing affected is make world?  It doesn't make sense.

Andrew


On Sun, 9 Feb 1997, Andrew Herdman wrote:

> Ok, finally managed to do that (make world rebuilds make and strips off
> the symbols grrrrr..)
> 
> On Sun, 9 Feb 1997, Poul-Henning Kamp wrote:
> 
> > 
> > Hey Cool!
> > 
> > Now for an encore, try to make "make" with -static so we don't have
> > to fight shared libs in gdb.
> > 
> > I would expect 807d432() to be free(3) but that is merely a guess...
> 
> (gdb) bt
> #0  0x1efd5 in kill ()
> #1  0x1ea33 in abort ()
> #2  0x1d787 in fstat ()
> #3  0x1d7af in fstat ()
> #4  0x1e642 in fstat ()
> #5  0x1e7e6 in free ()
> #6  0x12241 in Lst_Destroy (l=0x274e0, freeProc=0x1e7b0 <free>)
>     at /usr/src/usr.bin/make/lst.lib/lstDestroy.c:94
> #7  0xcfbb in Parse_End () at /usr/src/usr.bin/make/parse.c:2556
> #8  0x9b44 in main (argc=3, argv=0xefbfd77c)
>     at /usr/src/usr.bin/make/main.c:808
> 
> > >Well I had some courage.  I can reliably reproduce the bug, and have with
> > >a make re-compiled with -g, and the malloc trick i now have a nice core
> > >file.  As for using gdb for debugging... err well I don't now much about
> > >it... i've seen the bt command used extensively and this is what i got:
> > >
> > >Core was generated by `make'.
> > >Program terminated with signal 6, Abort trap.
> > >Cannot access memory at address 0x654f0.
> > >#0  0x807de11 in ?? ()
> > >(gdb) bt
> > >#0  0x807de11 in ?? ()
> > >#1  0x807d6e3 in ?? ()
> > >#2  0x807c232 in ?? ()
> > >#3  0x807c270 in ?? ()
> > >#4  0x807d24b in ?? ()
> > >#5  0x807d432 in ?? ()
> > >#6  0x12731 in Lst_Destroy (l=0x588c0, freeProc=0)
> > >    at /usr/src/usr.bin/make/lst.lib/lstDestroy.c:99
> > >#7  0xfb2b in TargFreeGN (gnp=0x55d00) at targ.c:219
> > >#8  0x1270b in Lst_Destroy (l=0x182e0, freeProc=0xfae0 <TargFreeGN>)
> > >    at /usr/src/usr.bin/make/lst.lib/lstDestroy.c:93
> > >#9  0xf9d7 in Targ_End () at targ.c:139
> > >#10 0xa000 in main (argc=3, argv=0xefbfd798) at main.c:804
> > >
> > >
> > >I have the core and the program that created, and if you want I can leave
> > >them somewhere for someone who knows what they are doing to take a peek at
> > >them.  I will help where I can of course, but this one is bigger than I
> > >am.
> 
> 
> Andrew
> 
>