From owner-freebsd-current Fri May 3 5:49:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6A04D37B41B for ; Fri, 3 May 2002 05:49:21 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 9C45A5346; Fri, 3 May 2002 14:49:16 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: housel@acm.org (Peter S. Housel) Cc: freebsd-current@freebsd.org Subject: Re: Can't su References: From: Dag-Erling Smorgrav Date: 03 May 2002 14:49:15 +0200 In-Reply-To: Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG housel@acm.org (Peter S. Housel) writes: > Current -CURRENT won't let me run "su"; it dies with SIGSEGV. The > backtrace says: Yep, I see what the error is. All I can say is "arrrgh!" since I've been running this code for a while now and it never segfaults on my box :( DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message