Hi Andrzej, On Tuesday 11 of February 2014 12:43:53 Andrzej Kaczmarek wrote: > --- > android/README | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/android/README b/android/README > index e3c314f..c7145d5 100644 > --- a/android/README > +++ b/android/README > @@ -108,6 +108,22 @@ be found at https://backports.wiki.kernel.org. Sample > kernels using backports for running BlueZ on Android are available at > https://code.google.com/p/aosp-bluez. > > +Running with Valgrind > +===================== > + > +BlueZ for Android is preconfigured to be easily run under Valgrind > memcheck. +Appropriate configuration and required modules are automatically > included when +building either userdebug or eng variant of Android > platform. > + > +Valgrind can be enabled in runtime by setting > "persist.sys.bluetooth.valgrind" +property to either literal "true" or any > numeric value >0. For example: +adb root > +adb shell setprop persist.sys.bluetooth.valgrind true > + > +After changing property value Bluetooth need to be restarted to apply > changes +(this can be done using UI, just disable and enable it again). > Property is +persistent, i.e. there's no need to enable Valgrind again > after reboot. + > ============================= > Building and running on Linux > ============================= Pushed, thanks. -- BR Szymon Janc -- 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
