New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 681510 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 24
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

asan_device_setup.sh not working for NVIDIA Shield TV

Reported by mkrasow...@opera.com, Jan 16 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: Android 6.0, SHIELD Android TV SW Version 3.3(24.18.78.174) Build MRA58K.324774_793.8284

What steps will reproduce the problem?
(1) ./tools/android/asan/third_party/asan_device_setup.sh

What is the expected result?
Asan wrapper get's delivered, system reboots ready to debug memory problems. Like when using ./third_party/android_tools/ndk/toolchains/llvm/prebuilt/linux-x86_64/bin/asan_device_setup

What happens instead?
>> Remounting /system rw
adbd is already running as root
remount succeeded
Target architecture: arm
Target architecture: aarch64
>> ASan runtime library not found

NVidia shield has userdev image installed.

Adding following options seems to do the thing, but some system services start to crash on boot, causing a bootloop (see the attached log.txt logcat)
  --lib third_party/llvm-build/Release+Asserts/lib/clang/4.0.0/lib/linux/libclang_rt.asan-arm-android.so

It would be fabulous to have a solution that would influence only the apk being debugged, rather than the whole OS.
 
log.txt
2.8 MB View Download

Comment 1 Deleted

Description: Show this description
Description: Show this description
Description: Show this description
Cc: -karandeepb@chromium.org
[Don't have any context on this]
The closest we have to running a single app with asan is
https://source.android.com/devices/tech/debug/asan.html#using_the_wrap_property

You'll need to write the "asanwrapper" script, it could be as simple as
  LD_PRELOAD=/path/to/libclang_rt.asan-*.so exec "$@"

I'm not sure it would help though, because that would still run at least one app_process under ASan (it has to!), and the logs show the 64-bit instance failing. Maybe you'd have better luck if your app is 32-bit.

I don't know enough about this device to understand the problem. Could be an old, or customized version of Android. ASan generally works fine on 64-bit-enabled devices. A symbolized stack trace could help.
Labels: Needs-Feedback
Can this issue be closed out?
Status: WontFix (was: Untriaged)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Sign in to add a comment