[GRASS-dev] [GRASS GIS] #617: r.sim.water crashes on WinGrass

[GRASS GIS]

#617: r.sim.water crashes on WinGrass
-----------------------------------+----------------------------------------
 Reporter:  hamish                 |       Owner:  grass-dev at lists.osgeo.org
     Type:  defect                 |      Status:  new                      
 Priority:  normal                 |   Milestone:  6.4.0                    
Component:  Raster                 |     Version:  6.4.0 RCs                
 Keywords:  wingrass, r.sim.water  |    Platform:  MSWindows XP             
      Cpu:  x86-32                 |  
-----------------------------------+----------------------------------------
 As reported on grass-user by Bernd Tyrna:
 (I can reproduce it on wingrass using the spearfish.sh test script in the
 source dir; on linux it is fine)

 {{{
 Hello!

 Has anyone experience with using r.sim.water under Windows? I'm planning
 to
 use it for the simulation of flash flood events.
 I tried it with a DEM (1m resolution) with the following region setting:

 g.region -p

 rojection: 99 (Transverse Mercator)
 zone:       0
 datum:      potsdam
 ellipsoid:  bessel
 north:      5377000.5
 south:      5375999.5
 west:       3502999.5
 east:       3504000.5
 nsres:      1
 ewres:      1
 rows:       1001
 cols:       1001
 cells:      1002001

 I calculated the first order partial derivative dx and dy with
 r.slope.aspect
 (Do I have to use degrees in the settings?)

 Leaving everything else unchanged for a testrun, I get the following
 message
 and r.sim.water crashes:

 "r.sim.water.exe hat ein Problem festgestellt und muss beendet werden."
 ("r.sim.water.exe has detected a problem and has to be closed")

 Can anyone tell me what's going wrong? Would it be better to use GRASS
 under
 Linux for this purpose?

 Thanks for your help,

 Bernd
 }}}


 with "g.gisenv set="DEBUG=3" set I can see that it happens after "Running
 MAY 10 version," text. Next step in the program after that is to allocate
 memory...... so I'm guessing it's a malloc problem that is only triggered
 on windows, much like we saw in r.los in bug #111 (and I expect we'll see
 a lot more of these).

 valgrind running now (slow),



 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/617>
GRASS GIS <http://grass.osgeo.org>