From: Arjen M. <Arj...@de...> - 2017-07-03 18:22:49
|
Hi Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Saturday, July 01, 2017 11:08 PM > > Hi Arjen: > > After reviewing the code, I spotted a fundamental error in the Windows variant of > the three-semaphores case which is that code used three Windows mutexes rather > than three named Windows semaphores. When I originally coded that variant, I > naively assumed that a two-state semaphore was effectively the same as a mutex, > but the semantics are slightly different, and now that I have discovered named > Windows semaphores I would prefer to use them to keep the Windows variant of > the 3-semaphores approach as close as possible to the Posix variant of this > approach. Therefore, I have now (commit b779495) addressed this issue by using > named Windows semaphores in the Windows variant of the three semaphores > approach, but I cannot even build test this modified Windows variant of the three- > semaphores approach here. So I need you to do that. I rebuilt PLplot using this latest commit and it all worked fine :). So the three-semaphores approach you have now implemented was the right way. I will try and see whether I can get the same result with the MSVC compiler. > > To be specific about what test I want you to run, please freshly configure PLplot > with the -DPLPLOT_WX_DEBUG_OUTPUT=ON option (which adds lots of useful > information if there are any remaining errors with the three-semaphores approach). > Unless you think this is necessary, given the completely positive results, I will concentrate on MSVC. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |