bamfdaemon crashed with SIGSEGV in __GI___libc_free()

Bug #1159240 reported by omer geziciler on 2013-03-23
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)

Bug Description

i I've been trying to shut down chromium

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: bamfdaemon 0.4.0daily13.03.07-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
Date: Sat Mar 23 23:21:06 2013
ExecutablePath: /usr/lib/i386-linux-gnu/bamf/bamfdaemon
InstallationDate: Installed on 2013-03-13 (10 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130313)
MarkForUpload: True
ProcCmdline: /usr/lib/i386-linux-gnu/bamf/bamfdaemon
 Segfault happened at: 0xb6b8b0f6 <free+38>: mov -0x4(%ecx),%ecx
 PC (0xb6b8b0f6) ok
 source "-0x4(%ecx)" (0x0000000b) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bamf
 free () from /lib/i386-linux-gnu/
 ?? () from /lib/i386-linux-gnu/
 g_free () from /lib/i386-linux-gnu/
 g_strfreev () from /lib/i386-linux-gnu/
 ?? ()
Title: bamfdaemon crashed with SIGSEGV in free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

omer geziciler (omergex) wrote :
information type: Private → Public

 __GI___libc_free (mem=0xf) at malloc.c:2892
 standard_free (mem=0xf) at /build/buildd/glib2.0-2.35.8/./glib/gmem.c:98
 g_free (mem=0xf) at /build/buildd/glib2.0-2.35.8/./glib/gmem.c:252
 g_strfreev (str_array=0x8ecc398) at /build/buildd/glib2.0-2.35.8/./glib/gstrfuncs.c:2405
 bamf_application_dispose (object=0x8de73c8) at bamf-application.c:911

Changed in bamf (Ubuntu):
importance: Undecided → Medium
summary: - bamfdaemon crashed with SIGSEGV in free()
+ bamfdaemon crashed with SIGSEGV in __GI___libc_free()
tags: removed: need-i386-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in bamf (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers