atop crashed with SIGFPE in __libc_start_main()

Bug #1432443 reported by Eustachy Motyka
268
This bug affects 3 people
Affects Status Importance Assigned to Milestone
atop (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

error crash

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 i686
ApportVersion: 2.16.2-0ubuntu3
Architecture: i386
Date: Mon Mar 16 00:00:01 2015
ExecutablePath: /usr/bin/atop
InstallationDate: Installed on 2014-12-10 (95 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141209)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20150316 600
ProcEnviron:
 SHELL=/bin/sh
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x8049eb0, argc=5, argv=0xbfb1c074, init=0x8066700, fini=0x8066770, rtld_fini=0xb773f140 <_dl_fini>, stack_end=0xbfb1c06c) 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
Eustachy Motyka (eusmotyka) 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 Security → Public Security
tags: removed: need-i386-retrace
Revision history for this message
Alexander Kops (alexkops) wrote :

The linked bug doesn't exist...
https://bugs.launchpad.net/bugs/1373639

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Thanks Alexander, I've opened the visibility of the other bug.

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 Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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