From owner-freebsd-current  Sat Jan 20 21:01:32 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA14675
          for current-outgoing; Sat, 20 Jan 1996 21:01:32 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA14667
          Sat, 20 Jan 1996 21:01:28 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id WAA19075; Sat, 20 Jan 1996 22:04:07 -0700
Date: Sat, 20 Jan 1996 22:04:07 -0700
From: Nate Williams <nate@sri.MT.net>
Message-Id: <199601210504.WAA19075@rocky.sri.MT.net>
To: jdp@FreeBSD.org
Cc: freebsd-current@FreeBSD.org
Subject: Re: problems in -current (was Re: awk broken ???)
In-Reply-To: <199601210426.MAA13402@linux.csie.nctu.edu.tw>
References: <199601210426.MAA13402@linux.csie.nctu.edu.tw>
Sender: owner-current@FreeBSD.org
Precedence: bulk

Chien-Ta Lee writes:
> Nate writes:
> > 2) John Polstra's change which affected all shlibs.
> > jdp         96/01/16 16:03:10
> > 
> >   Modified:    share/mk  bsd.lib.mk
> >   Log:
> >   Always link /usr/lib/c++rt0.o into a shared library.  CPLUSPLUSLIB is no
> >   longer necessary, and can be removed from Makefiles.
> > 
> > Unfortunately, I suspect the latter, but have no way of checking it
> > right now.
> 
> 	Ya...you are right, after back out this change, the system is
> 	happy again....No more awk problem, no more "malloc warning ...."
> 	Thanks.

Any ideas John?  It appears to be the culprit, either directly or
indirectly.  Is it possible something corrupting the stack, which would
show up as random cores later on?



Nate