Ticket #968 (closed defect: fixed)
v.net.salesman problem with memory allocation
|Reported by:||marisn||Owned by:||grass-dev@…|
v.net.salesman does something wrong during memory allocation. Normaly it results into assertion in malloc call.
v.net.salesman: malloc.c:4633: _int_malloc: Assertion `victim->fd_nextsize->bk_nextsize == victim' failed.
Valgrind reports invalid write (will attach full valgrind output as an attachment).
Number of cities:  ==6589== Invalid write of size 8 ==6589== at 0x401FAF: main (main.c:209) ==6589== Address 0xd18cbc8 is 0 bytes after a block of size 40 alloc'd ==6589== at 0x4C25EE5: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==6589== by 0x529118F: G__malloc (alloc.c:41) ==6589== by 0x401F64: main (main.c:207)
GRASS 6.4 r41215 on ~AMD64 Gentoo. 6.5 is also affected.
I'm unable to reproduce with Spearfish. Will attach sample dataset.