Am 28.08.2013 um 15:09 schrieb Nikola Pajkovsky:
Hello Erik,
"Erik K." <ummeegge(a)ipfire.org> writes:
> Dear IPTraf developers,
> i want to report a problem with iptraf-ng 1.1.4.
> If the logging option was enabled over the "Current Settings", iptraf-ng
stops after a little while with a "Floating point exception".
I'm having trouble to understand what do you mean by words "over the
Current Settings". Could you please paste here backtrace?
$ sudo gdb --args ./iptraf-ng -i wlan0 -L ./t
... pres 'r' and when it crash, run 'bt' ...
0x0000000000413353 in tcplog_flowrate_msg (buf=buf@entry=0x7fffffff7c00 "",
entry=0x812540, bufsize=64, entry=0x812540) at src/tcptable.c:442
442 rate_print(entry->bcount / interval, rbuf, sizeof(rbuf));
(gdb) bt
#0 0x0000000000413353 in tcplog_flowrate_msg (buf=buf@entry=0x7fffffff7c00 "",
entry=0x812540, bufsize=64, entry=0x812540) at src/tcptable.c:442
#1 0x00000000004150d5 in updateentry (table=table@entry=0x7fffffff7f70,
tableentry=0x812540, transpacket=0x7fffffffe22a, packet=packet@entry=0x7fffffffe208
"$w\003[\254\204",
linkproto=<optimized out>, packetlength=<optimized out>, bcount=52,
fragofs=64, logging=1, revlook=revlook@entry=0x7fffffff7ea8, rvnfd=0, logfile=0x7fdc30) at
src/tcptable.c:688
#2 0x000000000041140b in ipmon (facilitytime=0, ifptr=0x7fffffffe814 "wlan0")
at src/itrafmon.c:1052
#3 0x000000000040331d in main (argc=5, argv=0x7fffffffe568) at src/iptraf.c:519
--
Nikola
Hello Nikola,
thanks for your quick answer. I meant the usual iptraf-ng configuration window and not the
commandline. I use iptraf-ng in the IPFire distribution and there is no gdb available,
sorry for the less information which i could give to analyze the problem in a more clearer
way.
IPFire uses other interface names, so there is no wlan0 available but i used all IPFire
interfaces in IPFire labeled names. IPFire marks their interfaces with green0, blue0
(which is wlan0) orange0 and red0 and the problem occurs in each of them also by the
choice of "All Interfaces" but only in "IP traffic monitor" as far as
i could track it until now.
The patch from Vitezslav seems to solve the "Floating point exception" i make
some further tests and if problems appears, i will report it here.
Thanks for your work.
Greetings
Erik