atop crashed with SIGFPE in __libc_start_main()

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

Bug Description

atop crashed with SIGFPE in __libc_start_main()

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: atop 1.26-2
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 13 22:26:17 2015
ExecutablePath: /usr/bin/atop
ExecutableTimestamp: 1361826873
InstallationDate: Installed on 2014-07-10 (246 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20150313 600
ProcCwd: /
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x402c70, argc=5, argv=0x7fff62457da8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fff62457d98) at libc-start.c:287
 ?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
dinamic (dinamic6661) 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 #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.

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.