vnstat crashed with SIGSEGV in strftime_l()

Bug #545653 reported by Neil Harris
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
vnstat (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: vnstat

segmentation fault, reported huge (terabytes) usage today.
Lucid 64 bit.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 23 18:23:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/vnstat
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: vnstat 1.10-0.1
ProcCmdline: vnstat -d
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7fbbf89cc045: mov 0x8(%rcx),%ecx
 PC (0x7fbbf89cc045) ok
 source "0x8(%rcx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vnstat
StacktraceTop:
 ?? () from /lib/libc.so.6
 strftime_l () from /lib/libc.so.6
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
Title: vnstat crashed with SIGSEGV in strftime_l()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Neil Harris (nah40) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strftime_internal (s=0x7fff7381f690 "p�s�\177", maxsize=16,
 *__GI___strftime_l (
 ?? ()
 ?? ()
 __libc_start_main (main=<value optimized out>,

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 vnstat (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Iulian Udrea (iulian)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in vnstat (Ubuntu):
status: New → Invalid
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.