#1710: Segfault in r.proj
---------------------+------------------------------------------------------
Reporter: huhabla | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Keywords: | Platform: Linux
Cpu: x86-64 |
---------------------+------------------------------------------------------
I have found a reproducible but irregular appearing segfault in r.proj
when using several threads. Looks like an OpenMP race condition?
This error is not reproducible with OMP_NUM_THREADS=1.
Here the gdb output and backtrace
{{{
GRASS 7.0.svn (ECAD):~/Geostat > gdb r.proj
(gdb) r input=g250_06 location="Corine LAEA ETRS89" mapset=PERMANENT --o
#1710: Segfault in r.proj
----------------------------+-----------------------------------------------
Reporter: huhabla | Owner: grass-dev@…
Type: defect | Status: new
Priority: major | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Keywords: r.proj, openmp | Platform: Linux
Cpu: x86-64 |
----------------------------+-----------------------------------------------
Comment(by mmetz):
Replying to [ticket:1710 huhabla]:
> I have found a reproducible but irregular appearing segfault in r.proj
when using several threads. Looks like an OpenMP race condition?
> This error is not reproducible with OMP_NUM_THREADS=1.
I have disabled parallelization in r52882. It worked in my tests, but that
was apparently pure luck. Maybe a separate cache for each thread is
needed.