From owner-freebsd-stable@FreeBSD.ORG Mon Oct 23 02:01:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F9E816A403 for ; Mon, 23 Oct 2006 02:01:22 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E61D43D60 for ; Mon, 23 Oct 2006 02:01:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3B3981A3C1A; Sun, 22 Oct 2006 19:01:22 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BDFD851211; Sun, 22 Oct 2006 22:01:19 -0400 (EDT) Date: Sun, 22 Oct 2006 22:01:19 -0400 From: Kris Kennaway To: Jeremy Messenger Message-ID: <20061023020119.GA30219@xor.obsecurity.org> References: <1161567368.30822.31.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: Do anyone has any problem with sem_open() crash? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 02:01:22 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 22, 2006 at 08:48:20PM -0500, Jeremy Messenger wrote: > I guess I am safe then as I can ignore these cores.. Thanks! Isn't kernel= =20 > supposed to be avoid the crash? I don't see any of crash before I upgrade= d =20 > to last night of RELENG_6. It's not a crash, it's a configure script testing whether the syscall exists, and the the test program gets the signal 12 to tell it that it doesn't. This is expected behaviour. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPCJvWry0BWjoQKURAmrLAKDKiRrHWvVMmsZ48zk0/p35M4vn3gCePljl 0uggVfmSxwYOgevGxPYgOjs= =FBJP -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--