[fpc-devel] semaphores and mutes

[Boian Mitov]

    Hi Peter,

I thought you ware part of the FreePascal team. If you don't have access to 
FTP, please let me know, and I will set account for you on one of my 
servers. I also believe the fix is important and should find its way to the 
Project at some point.
Thank you for your efforts!

  With best regards,
    Boian Mitov

--------------------------------------------------------------------
Mitov Software
http://www.mitov.com
--------------------------------------------------------------------


----- Original Message ----- 
From: "Peter Popov" <ppopov at tamu.edu>
To: "FPC developers' list" <fpc-devel at lists.freepascal.org>
Sent: Friday, June 20, 2008 6:10 PM
Subject: Re: [fpc-devel] semaphores and mutes


> Where do you want me to post it?
> Peter
>
> On Fri, 20 Jun 2008 17:37:58 -0500, Boian Mitov <mitov at mitov.com> wrote:
>
>>    Hi Peter,
>>
>> Thank you!
>> I am already working to implement the Semaphores, and Mutexes.
>> I need timeout. Can you please post the patch? This is actually very 
>> important issue, as the libraries use threads extensively, and share 
>> huge number of resources. The timeouts are needed to resolve deadlocks.
>>
>>   With best regards,
>>     Boian Mitov
>>
>> --------------------------------------------------------------------
>> Mitov Software
>> http://www.mitov.com
>> --------------------------------------------------------------------
>>
>>
>> ----- Original Message ----- From: "Peter Popov" <ppopov at tamu.edu>
>> To: "FPC developers' list" <fpc-devel at lists.freepascal.org>
>> Sent: Friday, June 20, 2008 3:32 PM
>> Subject: Re: [fpc-devel] semaphores and mutes
>>
>>
>>> Anyways, some time ago I debuged the issue and patched kylix's SynObjs 
>>> unit to cure that. Basically, the problem is, as expected, glibc. Older 
>>> version did not have sem_timedwait() implemented. Later glibc included 
>>> it, along with several new variants of the remaining semaphore 
>>> routines. So, based on what thread model is used (LinuxThreads or NTPL) 
>>> each semaphore routine is implemented several times. The thing is a 
>>> total mess. Anyways, if one explicitly instructs the kylix linker which 
>>> version of semaphore functions to use (they have to be consistent) 
>>> TEvent.WaitFor can be implemnted for any timeout. If there is interest 
>>> I can post the patch.
>>>
>>
>> _______________________________________________
>> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
>> http://lists.freepascal.org/mailman/listinfo/fpc-devel
>
>
>
> -- 
> |***********************************************|
> |                                               |
> |  Peter Popov,                                 |
> |                                               |
> |  608L Blocker Bldg.                           |
> |  Institute for Scientific Computation,        |
> |  Texas A&M University                         |
> |  College Station, Texas 77843-3404            |
> |-----------------------------------------------|
> |  Phone: +1 (979) 458-4644,                    |
> |  Fax: +1 (979) 845-5827                       |
> |                                               |
> |***********************************************|
> _______________________________________________
> fpc-devel maillist  -  fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-devel