[GRASS-dev] backporting new v.digit to the 6.2 branch

Hamish hamish_nospam at yahoo.com
Thu Apr 26 22:16:35 EDT 2007


Maciej Sieczka wrote:
> > what's more, v.digit in GRASS 6.3 segfaults on startup for me
> > currently.
> 
> Oh. For me it works OK in 6.3.
> 
> > Not an encouraging sign for the 6.3 version being mature enough to
> > backport.
> 
> > g.region rast=roads
> > v.digit -n test_dig_area
> > New empty map created.
> > ###wish gui flashes up then disappears###
> > Segmentation fault
> > 
> > gdb:
> > G63> gdb `which v.digit`
> > ..
> > (gdb) run -n test_map1
> > Starting program:
> > /usr/local/src/grass/grass63/dist.i686-pc-linux-gnu/bin/v.digit -n
> > test_map1 [Thread debugging using libthread_db enabled]
> > [New Thread 16384 (LWP 9024)]
> > New empty map created.
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 16384 (LWP 9024)]
> > 0x406e4a02 in Tcl_ParseCommand () from /usr/lib/libtcl8.3.so.1
..
> > same thing starting with:
> > G63> GRASS_WISH=wish8.4  v.digit -n test_map2
> 
> FWIW I build and run against tcl/tk 8.4.12. No crashes here.


Now I recall this is C+Tcl, so the runtime wish doesn't matter as much,
it's the version of the tcltk compile time headers that matter.
Most likely a feature new for tcltk 8.4 being used?


Hamish




More information about the grass-dev mailing list