maximus crashed with SIGSEGV

Bug #417319 reported by Ch@llenger
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maximus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: maximus

crash after 5 min after reboot post-install

ProblemType: Crash
Architecture: i386
Date: Sat Aug 22 13:21:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/maximus
Package: maximus 0.4.8-0ubuntu3
ProcCmdline: maximus
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
SegvAnalysis:
 Segfault happened at: 0x804c01b <g_slist_free@plt+6359>: orl $0x2,(%esi)
 PC (0x0804c01b) ok
 source "$0x2" ok
 destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: maximus
Stacktrace:
 #0 0x0804c01b in ?? ()
 #1 0x095648a0 in ?? ()
 #2 0x01e00048 in ?? ()
 #3 0x00000141 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Tags: ubuntu-unr
Title: maximus crashed with SIGSEGV
Uname: Linux 2.6.31-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

visibility: private → public
tags: removed: need-i386-retrace
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.