[GRASS5] v.in.ascii updates

[Hamish]

> >>>I finally got around to installing valgrind to check where the
> >>>memory leaks are.
> > ..
> > 
> >>Can you do the same for the driver?
..
> The module creates the driver as a new process (fork-exec). I think
> that  you have to use --trace-children=yes.

ok,

CMD="v.in.ascii in=test_pts.dat out=test4 --o"
valgrind -v --tool=addrcheck --leak-check=yes --trace-children=yes $CMD


Memcheck log: 
 http://bambi.otago.ac.nz/hamish/grass/memleak/v.in.ascii/memchk_child.txt


Look for process 2030 (dbf):

==2230== 36748400 bytes in 48100 blocks are definitely lost in loss record 15 of 16
==2230==    at 0x3414CFE5: calloc (vg_replace_malloc.c:176)
==2230==    by 0x3416AAB9: sqpInitStmt (alloc.c:30)
==2230==    by 0x804B09F: execute (dbfexe.c:58)
==2230==    by 0x804D5CA: db__driver_execute_immediate (execute.c:29)



Also graphical Massif test, heap growth analysis: (end of page)
  http://bambi.otago.ac.nz/hamish/grass/memleak/v.in.ascii/



Hamish