[GRASS-dev] r.mapcalc in trunk with pthreads broken
Markus Metz
markus.metz.giswork at googlemail.com
Thu May 17 04:04:05 EDT 2012
On Thu, May 17, 2012 at 7:33 AM, Glynn Clements
<glynn at gclements.plus.com> wrote:
>
> Markus Metz wrote:
>
>> I am observing corrupted output from r.mapcalc in trunk if compiled
>> --with-pthread. The result is not identical to the one obtained
>> --without-pthread. The mapcalc expression included the functions
>> eval(), min(), and max(), in case that helps. Open a ticket?
>
> Yes.
>
> Also, can you describe whether (and how) the behaviour is affected by:
>
> export WORKERS=1
>
> The WORKERS environment variable controls the maximum number of
> threads used; the default value is 8.
With WORKERS=1, the r.mapcalc result is identical to pthreads
disabled, i.e. correct. Do you need more info?
Markus M
More information about the grass-dev
mailing list