Date: Sun, 22 Oct 2006 22:01:19 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Jeremy Messenger <mezz7@cox.net> Cc: freebsd-stable@freebsd.org Subject: Re: Do anyone has any problem with sem_open() crash? Message-ID: <20061023020119.GA30219@xor.obsecurity.org> In-Reply-To: <op.thupyub59aq2h7@mezz.mezzweb.com> References: <op.thun54ec9aq2h7@mezz.mezzweb.com> <1161567368.30822.31.camel@shumai.marcuscom.com> <op.thupyub59aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 > supposed to be avoid the crash? I don't see any of crash before I upgraded > 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPCJvWry0BWjoQKURAmrLAKDKiRrHWvVMmsZ48zk0/p35M4vn3gCePljl 0uggVfmSxwYOgevGxPYgOjs= =FBJP -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061023020119.GA30219>