Date: Sun, 22 Oct 2006 21:30:40 -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: <20061023013040.GA25120@xor.obsecurity.org> In-Reply-To: <op.thun54ec9aq2h7@mezz.mezzweb.com> References: <op.thun54ec9aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 22, 2006 at 08:09:30PM -0500, Jeremy Messenger wrote: > Hello folks, >=20 > Last night, I have upgraded from July RELENG_6 to last night. I have =20 > reinstalled all of ports and I noticed that the log/messages is collectin= g =20 > a few of 'pid 14699 (conftest), uid 0: exited on signal 12 (core dumped)'= . =20 > I dig in the configure and found a location of crash. It is from =20 > sem_open(). I don't get that before I upgraded the RELENG_6. >=20 > http://people.freebsd.org/~mezz/test-sem_open.cc (took from configure's = =20 > conftest) That's "bad system call" - probably you don't have SYSVSEM support enabled. Kris --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPBtAWry0BWjoQKURAmQWAKCWK0sE0x1Ra1ZRibgtMAVcdJt2nACfX7AE i0BfklAKqRe69hgRKspGreA= =whsN -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061023013040.GA25120>