Date: Sun, 22 Oct 2006 21:28:27 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Kris Kennaway" <kris@obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: Do anyone has any problem with sem_open() crash? Message-ID: <op.thurtpot9aq2h7@mezz.mezzweb.com> In-Reply-To: <20061023020119.GA30219@xor.obsecurity.org> References: <op.thun54ec9aq2h7@mezz.mezzweb.com> <1161567368.30822.31.camel@shumai.marcuscom.com> <op.thupyub59aq2h7@mezz.mezzweb.com> <20061023020119.GA30219@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Oct 2006 21:01:19 -0500, Kris Kennaway <kris@obsecurity.org> wrote: > 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. Ok, thanks for explain. Cheers, Mezz > Kris -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.thurtpot9aq2h7>