From owner-freebsd-current Wed Nov 11 10:18:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15836 for freebsd-current-outgoing; Wed, 11 Nov 1998 10:18:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.hq.tis.com (relay.hq.tis.com [192.94.214.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15819 for ; Wed, 11 Nov 1998 10:18:36 -0800 (PST) (envelope-from stevek@tis.com) Received: by relay.hq.tis.com; id NAA08163; Wed, 11 Nov 1998 13:24:13 -0500 (EST) Received: from clipper.hq.tis.com(10.33.1.2) by relay.hq.tis.com via smap (4.1) id xma008108; Wed, 11 Nov 98 13:23:19 -0500 Received: from mufasa.va.tis.com (mufasa.va.tis.com [192.168.10.18]) by clipper.hq.tis.com (8.9.1/8.9.1) with ESMTP id NAA18342; Wed, 11 Nov 1998 13:15:08 -0500 (EST) Received: from localhost (stevek@localhost) by mufasa.va.tis.com (8.8.7/8.8.7) with SMTP id NAA15877; Wed, 11 Nov 1998 13:24:41 -0500 (EST) (envelope-from stevek@mufasa.va.tis.com) Date: Wed, 11 Nov 1998 13:24:41 -0500 (EST) From: Steve Kiernan To: freebsd-current@FreeBSD.ORG cc: Alexander Litvin Subject: Re: The infamous dying daemons bug Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Nov 1998, Alexander Litvin wrote: > > Though, when I tried to stress the system with 'make -j# buildworld', > something weird happened. Particularily, I got a corrupt ld built. > It happened several times -- sometimes it is a bootstrap ld, and > as a result my buildworld just stopped (ld running indefinitely). > The last time it was a dynamic ld which I 'managed' to install into > /usr/libexec/elf/ld (made installworld) -- I was forced to extract > binary from 3.0-RELEASE distribution, since my system was not > able to build anything. > > It may or may not be related to kernel stuff. The fact that it always > happen to ld makes me feel that it may be just build process coruption. > > Anybody seen things like this? Anybody interested in details? I've seen similar things happen on my 3.0-RELEASE system. If all running programs can remain paged in, the system runs fine. Once processes start getting swapped out, I get corruption when pages are paged in from swap. Header files get an occasional random character changed in them, shared libraries crash with SEGV errors (once libc.so became 'corrupted' and I had to reboot), builds fail randomly and the system basically goes into chaos and occassionally crashes. Since there's no a.out gdb compiled I went to compile the latest gdb with a.out support, but it blew up in syntax errors. What version of gdb will actually build on 3.0 with a.out support so I can debug my crash dumps? -- Stephen Kiernan stevek@tis.com TIS Labs at Network Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message