From: Szymon Janc <szymon.janc@tieto.com>
To: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/README: Add Valgrind description
Date: Tue, 11 Feb 2014 17:34:15 +0100 [thread overview]
Message-ID: <8190802.H0AKWduXNq@leonov> (raw)
In-Reply-To: <1392119033-23035-1-git-send-email-andrzej.kaczmarek@tieto.com>
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
prev parent reply other threads:[~2014-02-11 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 11:43 [PATCH] android/README: Add Valgrind description Andrzej Kaczmarek
2014-02-11 16:34 ` Szymon Janc [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8190802.H0AKWduXNq@leonov \
--to=szymon.janc@tieto.com \
--cc=andrzej.kaczmarek@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox