modem-manager crashed with SIGSEGV in match_info_new()

Bug #1018651 reported by madigor
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: modemmanager 0.6~git201206221719.8289a64-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic i686
ApportVersion: 2.2.5-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Jun 28 02:29:47 2012
ExecutablePath: /usr/sbin/modem-manager
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120606.2)
ProcCmdline: /usr/sbin/modem-manager
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb75de231 <g_match_info_unref+33>: lock cmpxchg %edx,(%esi)
 PC (0xb75de231) ok
 source "%edx" ok
 destination "(%esi)" (0xb76b16e0) in non-writable VMA region: 0xb767f000-0xb76ce000 r-xp /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.3302.0
SegvReason: writing VMA /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.3302.0
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 g_match_info_unref () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_match_info_free () from /lib/i386-linux-gnu/libglib-2.0.so.0
 mm_gsm_parse_clck_response ()
 ?? ()
 ?? ()
Title: modem-manager crashed with SIGSEGV in g_match_info_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
madigor (madigor) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 match_info_new (regex=0xa03abe0, string=0xe914c380 <Address 0xe914c380 out of bounds>, string_len=-1217718560, start_position=0, match_options=0, is_dfa=-1081531684) at /build/buildd/glib2.0-2.33.3/./glib/gregex.c:452
 mm_gsm_parse_clck_response (reply=0xa05e4b0 "", enabled=enabled@entry=0xbf89231c) at mm-modem-helpers.c:964
 get_facility_lock_state_done (port=0xa060130, response=0xa05a390, error=0x0, user_data=0xa03bc10) at mm-generic-gsm.c:1732
 handle_response (port=0xa060130, response=0xa04b380, error=0x0, callback=0x8064df0 <get_facility_lock_state_done>, callback_data=0xa03bc10) at mm-at-serial-port.c:134
 mm_serial_port_got_response (self=self@entry=0xa060130, error=0x0) at mm-serial-port.c:571

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 modemmanager (Ubuntu):
importance: Undecided → Medium
summary: - modem-manager crashed with SIGSEGV in g_match_info_unref()
+ modem-manager crashed with SIGSEGV in match_info_new()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in modemmanager (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

As far as I know this bug was fixed recently in Quantal, and the latest version available in the archive (0.6.0.0) addresses this issue.

Closing as Fix Released.

Changed in modemmanager (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I'm mixing this up, I think; I'll mark this as a duplicate of bug 1015328 instead, which seems more appropriate (and I'll upload the fix to THAT incessantly).

Changed in modemmanager (Ubuntu):
status: Fix Released → Triaged
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.