bluetoothd crashed with SIGSEGV in malloc_consolidate()

Bug #1725102 reported by 1Crimson1
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
New
Medium
Unassigned

Bug Description

Trying to connect NES30Pro from 8bitdo

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: bluez 5.46-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Thu Oct 19 22:27:42 2017
ExecutablePath: /usr/lib/bluetooth/bluetoothd
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: HP HP EliteBook 850 G3
ProcCmdline: /usr/lib/bluetooth/bluetoothd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a65dd27b-ea3c-438f-9194-1fe13412160c ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f5920c97108 <malloc_consolidate+312>: mov 0x8(%rbx),%rax
 PC (0x7f5920c97108) ok
 source "0x8(%rbx)" (0x100000007) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bluez
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f5920fe8c20 <main_arena>) at malloc.c:4489
 _int_malloc (av=av@entry=0x7f5920fe8c20 <main_arena>, bytes=bytes@entry=1265) at malloc.c:3705
 _int_realloc (av=av@entry=0x7f5920fe8c20 <main_arena>, oldp=oldp@entry=0x559f492c60e0, oldsize=oldsize@entry=640, nb=nb@entry=1280) at malloc.c:4626
 __GI___libc_realloc (oldmem=0x559f492c60f0, bytes=1264) at malloc.c:3245
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/08/2017
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.16
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.76
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 850 G3
dmi.sys.vendor: HP
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: E4:A4:71:DD:E5:04 ACL MTU: 1021:4 SCO MTU: 96:6
  DOWN
  RX bytes:828 acl:0 sco:0 events:36 errors:0
  TX bytes:392 acl:0 sco:0 commands:35 errors:0

Revision history for this message
1Crimson1 (crimson-syndicateunderground) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f5920fe8c20 <main_arena>) at malloc.c:4489
 _int_malloc (av=av@entry=0x7f5920fe8c20 <main_arena>, bytes=bytes@entry=1265) at malloc.c:3705
 _int_realloc (av=av@entry=0x7f5920fe8c20 <main_arena>, oldp=oldp@entry=0x559f492c60e0, oldsize=oldsize@entry=640, nb=nb@entry=1280) at malloc.c:4626
 __GI___libc_realloc (oldmem=0x559f492c60f0, bytes=1264) at malloc.c:3245
 dbus_realloc (memory=<optimized out>, bytes=<optimized out>) at ../../../dbus/dbus-memory.c:678

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in bluez (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1689446, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

information type: Private → Public
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.