[gdal-dev] Mutexes

Even Rouault even.rouault at spatialys.com
Mon May 3 08:26:14 PDT 2021


I don't see myself much value to the mutexes with timeout, at least in 
how they are used within GDAL. What you underline was actually reported 
in https://github.com/OSGeo/gdal/issues/3631. The fix would be to use a 
non-timeout mutex


Le 03/05/2021 à 17:23, Andrew Bell a écrit :
> Hi,
> I'm looking at code in gdalwarpkernel.cpp and there are calls to 
> CPLAcquireMutex that take a "timeout" argument. From looking at 
> cpl_multiproc, on a non-windows system it seems the timeout is 
> ignored, but on WIN32 it is respected in the call, but the return 
> value is generally ignored, meaning that the subsequent code could run 
> without the lock having been acquired.
> This seems like strange behavior. Is there a reason for the different 
> behavior on Windows and not-Windows? Am I missing something?
> Thanks,
> -- 
> Andrew Bell
> andrew.bell.ia at gmail.com <mailto:andrew.bell.ia at gmail.com>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

My software is free, but my time generally not.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20210503/745c5f3a/attachment-0001.html>

More information about the gdal-dev mailing list