Running bluetoothd from the build directory I noticed that as soon as
a bluetooth audio device was connect, bluetoothd would be disconnected
from dbus and print
Disconnected from D-Bus. Exiting.
Luiz Augusto von Dentz suggested trying with SELinux disabled and that
solved the problem.
This patch just documents how to disable SELinux before running
bluetoothd from the build directory. I would love to say more about
why that is needed, but could not find anything on the audit log.
The HACKING document says that Debian's automake version doesn't satisfy
the automake >= 1.10 requirement, but this is no longer true. The
automake version in Debian 8 (oldstable) is 1.14 and the version in
Debian 9 (stable) is 1.15.
Make use of -f option in the instruction of how to run bluetoothd from
the source tree since that doesn't require installing the main.conf
when testing new options.
Without --suppressions=./tools/valgrind.supp in valgrind cmd,
bluetoothd throws following error:
==1237== Syscall param socketcall.bind(my_addr.rc_bdaddr) points to uninitialised byte(s)
==1237== at 0x588B227: bind (syscall-template.S:81)
==1237== by 0x451545: logging_open (log.c:76)
==1237== by 0x451545: __btd_log_init (log.c:314)
==1237== by 0x40B035: main (main.c:610)
==1237== Address 0xfff0003b6 is on thread 1's stack
==1237== in frame #1, created by __btd_log_init (log.c:306)
==1237== Uninitialised value was created by a stack allocation
==1237== at 0x451490: __btd_log_init (log.c:306)
==1237==
==1237== Syscall param socketcall.bind(my_addr.rc_channel) points to uninitialised byte(s)
==1237== at 0x588B227: bind (syscall-template.S:81)
==1237== by 0x451545: logging_open (log.c:76)
==1237== by 0x451545: __btd_log_init (log.c:314)
==1237== by 0x40B035: main (main.c:610)
==1237== Address 0xfff0003b8 is on thread 1's stack
==1237== in frame #1, created by __btd_log_init (log.c:306)
==1237== Uninitialised value was created by a stack allocation
==1237== at 0x451490: __btd_log_init (log.c:306)
