[kde-freebsd] [CFT] kde-games fix for (invalid shared segment parameter)

Mel Flynn rflynn at acsalaska.net
Fri Mar 9 20:17:29 UTC 2012


On 3/9/2012 20:32, Alberto Villa wrote:
> On Fri, Mar 9, 2012 at 5:55 PM, Mel Flynn <rflynn at acsalaska.net> wrote:
>> I'm wondering two different things:
>> 1) Why are we using semaphore locks?
>> Traced this down to missing POSIX_THREAD_PROCESS_SHARED support
>> (basically, the pthread_mutexattr_setpshared POSIX function).
>>
>> 2) Could missing support of anonymous semaphores be the root cause? In
>> other words, has anyone looked into:
>> https://git.reviewboard.kde.org/r/102147/
>>
>> It makes sense to me that if we're unable to use KSDC that each program
>> creates it's own segments and we're consuming more then we should be.
> 
> If you're talking only about KSDC, yes, it was me who implemented
> semaphore support a couple of years ago (it has changed quite a bit
> since then). As far as I remember, starting from FreeBSD 9.X KSDC
> works fine with anonymous semaphores. I had an idea to write an
> implementation with named semaphores for 8.X, but never started. Also,
> I think that pshared locks were added to FreeBSD, but sysconf feature
> line wasn't updated. I'll search my archives.
> 
> Anyway, this cannot be the cause of the problems as 9.X and 10.X have
> a fully working KSDC.

Yet, in the log at http://seibercom.net/logs/.xsession-errors the lock
not supported message appears and he's supposedly on 9.0, so I wonder if
that is the cause of his phonon problems or that semaphore locks still
don't work on 9.0. Either way I'm going to make the apple patch FreeBSD
specific and see how my 8.2+kdelibs-4.7.4 is going to hold up.

-- 
Mel


More information about the kde-freebsd mailing list