Date: Wed, 12 Nov 2008 15:02:27 -0500 From: Mikhail Teterin <mi+mill@aldan.algebra.com> To: Daniel Eischen <deischen@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, stable@freebsd.org Subject: Re: dlopen-ing a library with OpenMP by a non-OpenMP process Message-ID: <491B3653.5080209@aldan.algebra.com> In-Reply-To: <Pine.GSO.4.64.0811121451260.4280@sea.ntplx.net> References: <491B1BD2.4050903@aldan.algebra.com> <20081112194350.GJ47073@deviant.kiev.zoral.com.ua> <491B3270.5080402@aldan.algebra.com> <Pine.GSO.4.64.0811121451260.4280@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Sent by Daniel Eischen:
> On Wed, 12 Nov 2008, Mikhail Teterin wrote:
>
>> Sent by Kostik Belousov:
>>> On Wed, Nov 12, 2008 at 01:09:22PM -0500, Mikhail Teterin wrote:
>>>
>>>> Hello!
>>>>
>>>> Currently, when a program built without OpenMP (-fopenmp) is trying
>>>> to dlopen a library, built with the feature, the result is a crash
>>>> from "bad system call":
>>>>
>>>> #0 0x00000008009a223c in ksem_init () from /lib/libc.so.7
>>>> #1 0x0000000800998a8f in sem_init () from /lib/libc.so.7
>> Uhm... That worked... I see... Shouldn't sem_init be nicer about it,
>> though? Thanks,
> Or perhaps you should read sem(4) ;-)
Daniel, what are saying? That it is all my own fault? Generic kernel
does not have sem in it... I build a port with an option (OpenMP), that
make perfect sense, and try to use it. Software crashes...
There is a bug -- and you, instead of contemplating a fix, are telling
me to read a man-page? Wow...
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?491B3653.5080209>