[GRASS-dev] [GRASS GIS] #3429: g.gui.iclass: segfault when loading vector layer

GRASS GIS trac at osgeo.org
Sat Nov 11 18:59:46 PST 2017


#3429: g.gui.iclass: segfault when loading vector layer
--------------------------+------------------------------------------
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  7.4.0
 Component:  wxGUI        |    Version:  svn-trunk
Resolution:               |   Keywords:  g.gui.iclass import segfault
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+------------------------------------------

Comment (by annakrat):

 Replying to [comment:5 mlennert]:
 > This allows me to open the vector file with the stored polygons. Thanks
 !
 > In the terminal, I get messages such as:
 >
 > {{{
 > G__open(read): Unable to open
 '/home/mlennert/GRASSDATA/nc_spm_08_grass7/user1/.tmp/moritz-
 ulb/vector/trAreas325320/frmt': No such file or directory
 > }}}
 >

 I noticed, but they don't seem to actually cause anything so I ignored it
 so far, but we should look at it too.

 >
 > > For the debugging, you need to (after attaching the process) press
 Continue to release the gui, then do things in gui and it then jumps in
 qtcreator to segfaults or breakpoints.
 >
 > Thanks for the hint ! Now I can get the module to crash, but the
 debugger indicates some completely different place in the code. But
 probably I don't understand the debugging in qtcreator enough, yet.

 This is more complicated case for debugging than normally since the C
 calls are made from the GUI. I think the actual crash happened elsewhere,
 but that is just a consequence of a problem happening before. The specific
 problem I found was that in function CopyMap in iclass/digit.py the
 Vect_close function was deleting the temporary vector (which causes
 segfault later on). At this point I don't understand the temporary vectors
 enough to fix it properly...

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3429#comment:6>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list