atop crashed with SIGFPE in __libc_start_main()

Bug #1656510 reported by Matthias Andree
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
atop (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

found this in the apport system software crashed notification on logging in

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: atop 1.26-2build1
ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Jan 14 00:50:18 2017
ExecutablePath: /usr/bin/atop
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20170114 600
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x402c00, argc=5, argv=0x7ffc8d478aa8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc8d478a98) at ../csu/libc-start.c:291
 ?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Matthias Andree (matthias-andree) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1623031, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in atop (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.