atop crashed with SIGFPE in __libc_start_main()

[Lonnie Lee Best]

This crash happened after login.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: atop 1.26-2build1
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 28 11:28:49 2016
ExecutablePath: /usr/bin/atop
InstallationDate: Installed on 2016-02-10 (17 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20160228 600
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x402c00, argc=5, argv=0x7ffffbd84368, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffffbd84358) at libc-start.c:289
 ?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1373639, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.