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

[GRASS GIS]

#2583: v.net: crash on Windows
-------------------------+--------------------------------------------------
 Reporter:  mlennert     |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  blocker      |   Milestone:  7.0.0                    
Component:  LibVector    |     Version:  svn-releasebranch70      
 Keywords:  v.net        |    Platform:  MSWindows 8              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by mlennert):

 Replying to [comment:8 neteler]:
 > Replying to [comment:7 annakrat]:
 > > I just don't like releasing grass with a serious bug when we haven't
 even tried to fix it.
 >
 > Well, it does not happen e.g. on Linux.
 >
 > > I am talking about postponing it max one week. Basically, my question
 is: can Markus Metz look at it soon enough?
 >
 > No idea.
 >
 > > If not, then we can probably release it now.
 >
 > Changes I see after RC1:
 >
 >  * r64200 diglib: add numerical stability to dig_test_for_intersection()
 >  * r64198 diglib: add numerical stability to
 dig_distance2_point_to_line()
 >  * r64196 diglib: add numerical stability to dig_x_intersect()
 >  * many changes in
 http://trac.osgeo.org/grass/log/grass/branches/releasebranch_7_0/lib/vector/Vlib

 These also do not respect the proposed release procedure:

 "Any commits from that point [RC] on can only be well-tested, non-invasive
 bug fixes."

 Many of these changes do not even seem to be bug fixes, but optimization.
 Typically the stuff that should have been tested in trunk and if stable
 integrated into the next point release...
 And, yes, tests should help, but they also would have to be run on
 different platforms before commits.

 And my level of understanding does not allow me to understand what in
 there might cause a MSWin-specific issue. My highest contender, in light
 of Martin's debug info above is r64215.

 Do I understand correctly that r64163 was just in time to be included into
 RC1 ?

 Martin, could you rerun your windows builds to get versions before and
 after the above change, or is that too much work ?

 Or maybe Glynn could have a look at these changes to see if there's
 anything obvious to more informed eyes than mine ?

 Moritz

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