Comment 0 for bug 1164023

Revision history for this message
Till Kamppeter (till-kamppeter) wrote : modem-manager crashed with SIGSEGV in g_slice_alloc()

Happened again, after some attempts to connect via mobile broadband.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.really-0ubuntu4
Uname: Linux 3.9.0-030900rc5-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 3 18:37:32 2013
ExecutablePath: /usr/sbin/modem-manager
InstallationDate: Installed on 2013-03-28 (5 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x7f7286b66f7f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7f7286b66f7f) ok
 source "(%rbx)" (0x100000001) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: modem-manager crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: