Ubuntu
atop package

atop crashed with SIGFPE in __libc_start_main()

Bug #1432119 reported by snowcrash on 2015-03-14

This bug report is a duplicate of: Bug #1022865: atop crash with SIGFPE in acctprocnt(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	atop (Ubuntu)	New	Undecided	Unassigned

Bug Description

$ lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04

$ apt-cache policy atop
atop:
  Installiert: 1.26-2
  Installationskandidat: 1.26-2
  Versionstabelle:
*** 1.26-2 0
        500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

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-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
Date: Fri Mar 6 23:50:45 2015
ExecutablePath: /usr/bin/atop
InstallationDate: Installed on 2014-03-17 (361 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20150306 600
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
Signal: 8
SourcePackage: atop
StacktraceTop:
?? ()
?? ()
__libc_start_main (main=0x402c70, argc=5, argv=0x7fffc5b09548, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc5b09538) at libc-start.c:287
?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: Upgraded to vivid on 2015-03-05 (8 days ago)
UserGroups:

Tags:

Revision history for this message

snowcrash (mail-t-alex) wrote on 2015-03-14:

Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2015-03-14: 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.