Ubuntu
bluez package

bluetoothd crashed with SIGSEGV in calloc()

Bug #351120 reported by Michael on 2009-03-29

This bug report is a duplicate of: Bug #337080: bluetoothd crashed with SIGSEGV in calloc(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Binary package hint: bluez

trying to read a Motorola PC850. Then the program crashed.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/bluetoothd
Package: bluez 4.32-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/bluetoothd
ProcEnviron: PATH=(custom, no user)
Signal: 11
SourcePackage: bluez
StacktraceTop:
?? () from /lib/tls/i686/cmov/libc.so.6
calloc () from /lib/tls/i686/cmov/libc.so.6
dbus_malloc0 () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
Title: bluetoothd crashed with SIGSEGV in calloc()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Tags:

Revision history for this message

Michael (y2k103) wrote on 2009-03-29:

Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (515 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (718 bytes, text/plain; charset="utf-8")
Registers.txt Edit (459 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-31: Symbolic stack trace

Stacktrace.txt (retraced) Edit (6.2 KiB, text/plain)

StacktraceTop:_int_malloc (av=0xb7f4c140, bytes=32) at malloc.c:4171
__libc_calloc (n=32, elem_size=1) at malloc.c:3946
dbus_malloc0 (bytes=40) at dbus-memory.c:524
_dbus_timeout_new (interval=25000,
_dbus_pending_call_new_unlocked (connection=0xb96b0f70,