bluetoothd crashed with SIGSEGV in free()

Bug #409560 reported by Andres Monroy-Hernandez
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: bluez

Crashed unexpected list

ProblemType: Crash
Architecture: i386
Date: Wed Aug 5 17:39:45 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/bluetoothd
Package: bluez 4.45-0ubuntu4
ProcCmdline: /usr/sbin/bluetoothd --udev
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x27c203: cmp 0xc(%eax),%esi
 PC (0x0027c203) ok
 source "0xc(%eax)" (0xd000366f) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 free () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
Title: bluetoothd crashed with SIGSEGV in free()
Uname: Linux 2.6.31-3-generic i686
UserGroups:

Revision history for this message
Andres Monroy-Hernandez (andresmh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:malloc_consolidate (av=<value optimized out>)
_int_free (av=<value optimized out>, p=0xd4cb78)
*__GI___libc_free (mem=0xd4cb80) at malloc.c:3716
_dl_close_worker (map=0xd4c8d0) at dl-close.c:624
_dl_close (_map=0xd4c8d0) at dl-close.c:742

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in bluez (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Can this issue be reproduced? Are you still seeing this on newer releases of Ubuntu?

Changed in bluez (Ubuntu):
status: New → Incomplete
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.