Hi Stuart, > >>> however could you try to get a backtrace with gdb as well since it seems > >>> that valgrind either distorts or hides some errors. > >> I guess that I have forgotten how to use gdb because the backtrace > >> doesn't tell me much. Or perhaps I have to recompile with "-g". > > if you use ./bootstrap-configure it will automatically enable it. If not > > then give --enable-debug to configure. And make sure you do a make clean > > before that. > > This what I did (from history) > > 17 git clone git://git.kernel.org/pub/scm/bluetooth/bluez.git && cd bluez && ./bootstrap-configure && make > 18 ./bootstrap-configure && make > > I ran the bootstrap-configure twice because I had to install gtk-doc. > > :; grep ' -g' Makefile > CFLAGS = -Wall -O2 -D_FORTIFY_SOURCE=2 -fPIC -g -O0 that is indeed strange. You should be able to get a proper backtrace. > I thus think that I did compile with -g and that I cannot get a stack trace > because someone has written all over the stack. > > [I'm trying to remove btusb but I think that I'll need a reboot > :; lsmod | grep btusb > btusb 12056 11465 > bluetooth 49632 1 btusb > ] Normally hciconfig hci0 down and killing bluetoothd should be enough. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
