Date: Sat, 20 Jan 1996 21:08:04 -0800 From: John Polstra <jdp@polstra.com> To: Nate Williams <nate@sri.MT.net> Cc: freebsd-current@FreeBSD.org Subject: Re: problems in -current (was Re: awk broken ???) Message-ID: <199601210508.VAA29770@austin.polstra.com> In-Reply-To: Your message of "Sat, 20 Jan 1996 22:04:07 MST." <199601210504.WAA19075@rocky.sri.MT.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Egads! :-( > 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? Is it possible that, when the shared libraries such as libc are being built, there is still the _old_ version of c++rt0.o in /usr/lib? It _looks_ to me like c++rt0.o is built and installed before the shared libraries are built, but I'm not _at all_ sure. If the libraries were being built with the old c++rt0.o, it would definitely cause problems. Though, again, it seems unlikely they'd explain the actual symptoms that are being seen. Anyway, I'll take yet another look at it, and see if I can come up with any ideas about what's going on. -- John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601210508.VAA29770>