Comment 6 for bug 188897

I can confirm the bug with itop 0.1-1build1. A rebuild in pbuilder did not fix it. Itop crashed frequently at start-up.
My system is also an amd64.
As itop did not create a proper stacktrace, I rebuilt itop with:
- strip removed from src/Makefile
- option -ggdb added as option to gcc in src/Makefile
- pkg-create-dbgsym added as build-dependency

Running itop from the resulting itop and itop-dbgsym packages gave a proper backtrace (attached).
Analysis shows cur_no = 503. However, cur_no is used as index for an array (interrupts) with size 256 (defined as MAX_INTS in src/config.h), so the array index is out of bounds.
Rebuilding itop with MAX_INTS=1024 instead of 256 solves the issue. As cur_no gets set from the first 3 characters on each string read from /proc/interrupts, it can have maximum 3 digits. Therefore MAX_INTS=1024 should be a safe value to use.