package iftop
version 0.17-16
severity important
thanks
The problem still persists, malloc(3) causes segfaults.
$ iftop -i eth0 -i eth0
produces a plain segmentation fault printout, as also
$ iftop -N -i eth0 -i eth0
does. The variation
$ iftop -i eth0 -i eth0 -N
even produces a back trace complaining on
"malloc(): memory corruption (fast)"
and finally the variation
$ iftop -N -N
enters a silent infinite loop, consuming all available resources.
Presently I suspect the problem to be located in 'stringmap.c',
in either of stringmap_delete(), stringmap_delete_free(), or
stringmap_insert(). The code is convoluted enough to hide
manipulations of the allocated memory regions. I see no other
plausible cause for malloc(3) to generate a segmentation fault
later on.
Regards,
Mats Erik Andersson, fil. dr
Abonnerar på: debian-mentors, debian-devel-games, debian-perl,
debian-ipv6, debian-qa
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
