From owner-freebsd-current Mon Dec 22 00:40:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA08816 for current-outgoing; Mon, 22 Dec 1997 00:40:46 -0800 (PST) (envelope-from owner-freebsd-current) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA08803 for ; Mon, 22 Dec 1997 00:40:42 -0800 (PST) (envelope-from detlev!joelh@wcc.wcc.net) Received: from detlev.UUCP (ppp102.wcc.net [208.6.232.102]) by wcc.wcc.net (8.8.7/8.8.7) with ESMTP id CAA07645 for ; Mon, 22 Dec 1997 02:37:44 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.7/8.8.7) id CAA01940 for freebsd-current@freebsd.org; Mon, 22 Dec 1997 02:37:17 -0600 (CST) (envelope-from joelh) Date: Mon, 22 Dec 1997 02:37:17 -0600 (CST) From: Joel Ray Holveck Message-Id: <199712220837.CAA01940@detlev.UUCP> To: freebsd-current@freebsd.org Subject: Random core dumps Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm getting some odd core dumps here... In case you can't guess from my last two messages, I have just rebuilt and installed all changed utilities since I installed -current on 28 November. (Now, I know, I should do a make world on the entire tree, but I only have 20--30 MB free at present. I suppose I can free up a few more megs here and there, but I don't think I could do an entire make world with 40 MB free, which is about what I could end up with.) However, now I'm getting random core dumps from utilities that weren't recompiled. So far, victims have included: - xconsole - emacs - inetd - sendmail - bash Does anybody know of any changes made to libc, include, or something like that, something that would require me to rebuild all my programs? If it's any help, bash dies with: -bash in free(): junk pointer, too high to followed by some invalid chunk message that I can't remember any more, and lost earlier. All the programs are exiting with sigsegv's. Any ideas? Thanks, joelh PS: The bash's have so far exited after getting an error on a prolonged make. Getting the same error after an immediate make didn't harm it.