#2814: digitizer crashes, leaves vector broken --------------------------+------------------------------- Reporter: harrikoo | Owner: grass-dev@… Type: defect | Status: new Priority: blocker | Milestone: 7.0.3 Component: wxGUI | Version: 7.0.2 Resolution: | Keywords: digitizer, vector CPU: Unspecified | Platform: Unspecified --------------------------+-------------------------------
Comment (by annakrat): Replying to [comment:9 mlennert]: > Replying to [comment:5 neteler]: > > Replying to [comment:4 mlennert]: > > > Found the change at fault: r64214. Now we need to identify what in that change causes the segfault. > > > > Cannot you run it all through "gdb" for a backtrace? > > Well, I've never managed to debug GUI issues via gdb, notably since g.gui.vdigit is a Python script, not a C-module. Do you have tips on how to debug such issues with gdb ? For this case I use gdb trough QtCreator, you can attach external process - the gui and if gui crashes, it will show where in the c code it happened. This is quite easy, there is a wiki on using QtCreator with GRASS[https://grasswiki.osgeo.org/wiki/Using_QtCreator_for_GRASS_C_development here] -- Ticket URL: <https://trac.osgeo.org/grass/ticket/2814#comment:10> GRASS GIS <https://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev