chkutmp crashed with SIGSEGV in _Unwind_Backtrace()

Bug #565578 reported by Jeff Lane 
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chkrootkit (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: chkrootkit

This happened after booting and during a dist-upgrade with updates as of 17 April 2010.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: chkrootkit 0.49-3
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
AssertionMessage: *** stack smashing detected ***: ./chkutmp terminated
Date: Sat Apr 17 16:01:27 2010
ExecutablePath: /usr/lib/chkrootkit/chkutmp
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: ./chkutmp
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7f5e54227af8: mov (%rsi),%rcx
 PC (0x7f5e54227af8) ok
 source "(%rsi)" (0x7fff7a002d7b) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chkrootkit
StacktraceTop:
 ?? () from /lib/libgcc_s.so.1
 _Unwind_Backtrace () from /lib/libgcc_s.so.1
 backtrace () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 __fortify_fail () from /lib/libc.so.6
Title: chkutmp crashed with SIGSEGV in _Unwind_Backtrace()
UserGroups:

Revision history for this message
Jeff Lane  (bladernr) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /lib/libgcc_s.so.1
 _Unwind_Backtrace () from /lib/libgcc_s.so.1
 *__GI___backtrace (array=<value optimized out>,
 __libc_message (do_abort=<value optimized out>,
 *__GI___fortify_fail (

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chkrootkit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in chkrootkit (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chkrootkit (Ubuntu) because there has been no activity for 60 days.]

Changed in chkrootkit (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jeff Lane  (bladernr) wrote :

Old bug

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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