[GRASS-dev] [GRASS GIS] #2583: v.net: crash on Windows

GRASS GIS trac at osgeo.org
Tue Feb 17 14:12:05 PST 2015


#2583: v.net: crash on Windows
--------------------------+-------------------------------------------------
  Reporter:  mlennert     |       Owner:  grass-dev@…              
      Type:  defect       |      Status:  closed                   
  Priority:  critical     |   Milestone:  7.0.0                    
 Component:  LibVector    |     Version:  svn-releasebranch70      
Resolution:  fixed        |    Keywords:  v.net                    
  Platform:  MSWindows 8  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------
Changes (by annakrat):

  * status:  reopened => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:32 mmetz]:
 > Replying to [comment:30 mlennert]:
 > > Replying to [comment:29 wenzeslaus]:
 > > > The test for v.net is now at 50%. This is a little bit suspicious.
 The values changed from yesterday before the last fixes (r64644, r64656).
 Test suite for v.net was added in r64639 and the values were obtained
 before the last fixes which can mean that r64644 or r64656 changed the
 results. Which results are the right ones? Is this even expected?
 > >
 > > MarkusM is the only one who can tell for sure, but I would not be
 surprised that changes in topology handling induce changes in primitive
 counts.
 >
 > The difference is caused by the fix for the uninitialized values in
 `v.net`, therefore I am sure that the new result is correct. Uninitialized
 double values (here: z coordinates) can have weird effects, I noticed that
 earlier somewhere else. Unfortunately, this bug has been present in
 `v.net` since GRASS 6.4.0 or earlier.

 OK, I updated the test with the new values.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2583#comment:33>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list