Dear Maintainer,
The atop service crashed with a segmentation fault on Debian 12.
Log snippet: atop[196073]: segfault at 8 ip 000055f29a9f4a80 sp
00007ffcba5be990 error 4 in atop[55f29a9f4000+2d000] likely on CPU 0
Code bytes: > 8b 04 25 08 00 00 00 0f 0b 0f 1f 80 00 00 00 00 41 57 41
56 41 55
The crash seems to be a NULL pointer dereference (accessing address
0x8). This occurred on a standard Debian 12 installation.
* What led up to the situation?
I use atop to monitor performance and hw utilization of my server.
I typically run atop interactively in a tmux - and I was doing this at
the time of the crash as well.
The atop service is running with default config.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I did not do anything specifically. Atop was just running by itself.
Again: Default config purely as it comes from the package.
* What was the outcome of this action?
N/A.
* What outcome did you expect instead?
I expect atop to not crash with segfault.