Package: itop
Version: 0.1-4+b2
running as "itop -n 1" same as "itop -n 5" etc crashes it.
Also it leaves the terminal in a really fucked up state, when even "reset"
command does not restore normal terminal behavior.
as root: itop -a -n 1 shows once the output then crashes:
INT NAME RATE MAX
0 [ 0 0 ] 0 Ints/s (max: 0)
readline: warning: turning off output flushing
root@myhostname:~#
The fact that there are only zeroes shown is related to the other itop bug I
just reported.
But on other machine the result is same, it once show the output, then crashes:
INT NAME RATE MAX
0 [ 0 0 ] 0 Ints/s (max: 0)
1 [ 0 0 ] 0 Ints/s (max: 0)
5 [ 0 0 ] 0 Ints/s (max: 0)
8 [ 0 0 ] 0 Ints/s (max: 0)
9 [ 0 0 ] 0 Ints/s (max: 0)
12 [ 0 0 ] 0 Ints/s (max: 0)
16 [8324 0 ] 0 Ints/s (max: 0)
18 [ 0 0 ] 0 Ints/s (max: 0)
23 [ 0 0 ] 0 Ints/s (max: 0)
24 [ 0 0 ] 0 Ints/s (max: 0)
25 [1717 0 ] 0 Ints/s (max: 0)
26 [7221 0 ] 0 Ints/s (max: 0)
27 [ 0 13131943 ] 0 Ints/s (max: 0)
28 [8445 0 ] 0 Ints/s (max: 0)
29 [6980 0 ] 0 Ints/s (max: 0)
30 [ 0 0 ] 0 Ints/s (max: 0)
31 [ 3 0 ] 0 Ints/s (max: 0)
32 [ 0 0 ] 0 Ints/s (max: 0)
33 [ 0 0 ] 0 Ints/s (max: 0)
34 [ 0 0 ] 0 Ints/s (max: 0)
35 [ 0 0 ] 0 Ints/s (max: 0)
36 [6625 1439 ] 0 Ints/s (max: 0)
37 [ 0 0 ] 0 Ints/s (max: 0)
readline: warning: turning off output flushing
user@myhostname
also the output seems wrong (nonsense names of interrupts) which is another bug
(good job, itop :)
