From owner-freebsd-current Wed Sep 13 02:59:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA19379 for current-outgoing; Wed, 13 Sep 1995 02:59:45 -0700 Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA19365 for ; Wed, 13 Sep 1995 02:59:28 -0700 Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.6.11/8.6.9) id LAA02754 for freebsd-current@freefall.cdrom.com; Wed, 13 Sep 1995 11:16:27 +0200 Date: Wed, 13 Sep 1995 11:16:27 +0200 From: "Christoph P. Kukulies" Message-Id: <199509130916.LAA02754@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: Re: sig11 Sender: current-owner@FreeBSD.org Precedence: bulk I tried ~dyson/exception.s with my -current kernel to no effect. All sorts of apps die with sig 11: Yesterday I had a reproducable effect: I wanted to build a new kernel (running a Aug 31 kernel), and got (during make depend): Sep 12 17:39:36 blues /kernel: pid 3016: awk: uid 0: exited on signal 6 Sep 12 17:39:37 blues /kernel: pid 3019: awk: uid 0: exited on signal 4 I then built awk NOSHARED and got around this. /usr/bin/login also chokes with sig 11 under a -current kernel. Looking what /usr/bin/login and /usr/bin/awk have in common wrt shared libs there is -lc.2 => /usr/lib/libc.so.2.2 (0x8052000) the only candidate. But the cause may lay somewhere else of course. BTW, I'm running a 486DX2/66, 32MB, IDE disks (bounce buffers). --Chris Christoph P. Kukulies kuku@gil.physik.rwth-aachen.de