Markus, when tracing problems, it's no use for --leak-check=yes --show-reachable=yes unless You plan to hunt down memory leaks. Also it's likely that on fine running system vagrind will show nothing, as bug might be compiler/optimisation/system core libs sensitive.
Just some hints, Maris. 2010/7/2, GRASS GIS <[email protected]>: > #1032: ErrorCommandExecution g.proj > ----------------------+----------------------------------------------------- > Reporter: sallar | Owner: grass-...@… > Type: defect | Status: new > Priority: critical | Milestone: 6.4.0 > Component: default | Version: 6.4.0 RCs > Keywords: g.proj | Platform: Linux > Cpu: x86-32 | > ----------------------+----------------------------------------------------- > > Comment(by neteler): > > I have added valgrind output (but here g.proj -p works) > > -- > Ticket URL: <http://trac.osgeo.org/grass/ticket/1032#comment:18> > GRASS GIS <http://grass.osgeo.org> > > _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
