modem-manager crashed with SIGSEGV in smc_notify_alloc()

[Tomas Cassidy]

This crash occurred after I unplugged my USB modem device from the computer.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: modemmanager 0.6.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.2-0ubuntu1
Architecture: amd64
Date: Wed Sep 19 10:00:07 2012
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x7fcadf6f195f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7fcadf6f195f) ok
 source "(%rbx)" (0x400000004) 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: Upgraded to quantal on 2012-09-10 (8 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 smc_notify_alloc (size=<optimized out>, pointer=<optimized out>) at /build/buildd/glib2.0-2.33.14/./glib/gslice.c:1466
 g_slice_alloc (mem_size=80) at /build/buildd/glib2.0-2.33.14/./glib/gslice.c:1005
 magazine_cache_pop_magazine (countp=0x58, ix=4294967295) at /build/buildd/glib2.0-2.33.14/./glib/gslice.c:722
 thread_memory_magazine1_reload (ix=4294967295, tmem=<optimized out>) at /build/buildd/glib2.0-2.33.14/./glib/gslice.c:794
 g_slice_alloc (mem_size=0) at /build/buildd/glib2.0-2.33.14/./glib/gslice.c:992

[Mathieu Trudel-Lapierre (cyphermox)]

I'm not sure what to make of this; all indicates there was a crash deep inside Glib, that's not really something directly affecting modemmanager, so I've reassigned this to the 'glib2.0' source package.

Are you still able to reproduce this crash? There has been changes to glib since this bug was reported, so this might have been fixed already.

[Tomas Cassidy (tomas-cassidy)]

I can't reproduce this bug. Haven't seen it happen again after the first crash.

[Launchpad Janitor (janitor)]

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