[GRASS-dev] [GRASS GIS] #1875: Wrong output of v.overlay.and between lines and polygon in 6.4.3

[GRASS GIS]

#1875: Wrong output of v.overlay.and between lines and polygon in 6.4.3
--------------------------+-------------------------------------------------
  Reporter:  GG1234       |       Owner:  grass-dev@…              
      Type:  defect       |      Status:  closed                   
  Priority:  normal       |   Milestone:  6.4.3                    
 Component:  LibVector    |     Version:  6.4.3 RCs                
Resolution:  fixed        |    Keywords:                           
  Platform:  MSWindows 7  |         Cpu:  x86-64                   
--------------------------+-------------------------------------------------

Comment(by mmetz):

 Replying to [comment:3 GG1234]:
 > Great ! It works !
 >
 > Thank you for the quick help and debug.
 > Since I'm there just a few additional questions :
 >
 > - QGS project file periodically and very regularly crashes QGIS, often
 when upgrading versions on my Windows OSGEO4W setup. About once every
 three months, per project which is quite a lot. Is it the same on Ubuntu
 or other Linux distributions ?
 > When I try repairing these files, it seems to me (but with little
 investigation) that openlayers plugin seem to be the cause. Am I the only
 one to suffer from this and if not could it be possible to make Qgis more
 stable with these files, loading only valid layers and poping the usual
 warning when necessary ?

 You will most probably get more feedback on the QGIS mailing list about
 these problems.


 > - When multiple Grass are setup with OSGEO4W, how can I know which Grass
 is used in the Qgis-Grass plugin and could it be possible to switch
 between Grass versions ? (more a OSGEO4W question) Same question but with
 a standalone Grass setup ?

 For Windows, this is probably hard-coded in QGIS. Better ask on the QGIS
 mailing list to make sure.

 > - Out of curiosity, what was the cause of this bug ? Was it a side
 effect of a code optimisation of the function ?

 Yes, it was a side effect of optimization. v.overlay was until recently
 terribly slow and had some bugs when overlaying areas areas, I fixed it in
 trunk but did not backport all fixes.

 > - Regarding the Avira message, to your opinion is it an Avira deffect or
 a Grass deffect ? Am I the only one having this ?

 An Avira mystery. I have a Windows machine for testing, also with Avira,
 and do not get this message.

 Markus M

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