diff options
| author | 2022-11-01 13:54:57 -0600 | |
|---|---|---|
| committer | 2022-12-02 15:22:24 +0000 | |
| commit | 383832ff5b2390f3dcd44592db071d504268787d (patch) | |
| tree | 7f23d864663b8fe297f28ca8569df867b036020b /libs/jpegrecoverymap/jpegencoderhelper.cpp | |
| parent | 1e2b1b5c06d2409a17fd4df4fa31434fb58b8ea1 (diff) | |
GraphicsEnv: Fix isDebuggable
Update the logic used in GraphicsEnv to decide whether shared objects
can be inserted into the process. This is used by Vulkan layers,
GLES layers, and ANGLE when deciding whether libraries from outside
packages can be used.
The new logic doesn't just use PR_GET_DUMPABLE which is no longer set
by default in platform debug builds. It also incorporates
ANDROID_DEBUGGABLE, which is defined when `debuggable` is true in
Android.bp. This happens for eng or userdebug builds of the platform.
The use of `debuggable` is the replacement for reading ro.debuggable
which can no longer be read at runtime (see b/193912100).
Tested with:
export APP_PACKAGE=<app from Play Store>
adb shell settings put global angle_debug_package org.chromium.angle
adb shell settings put global angle_gl_driver_selection_pkgs $APP_PACKAGE
adb shell settings put global angle_gl_driver_selection_values angle
Test: Released app able to load from angle_debug_package on userdebug
Test: Released app cannot use angle_debug_package on user build
Bug: b/193912100
Bug: b/253678459
Change-Id: I3dda4258e23871ee2fab2cf5ba367612e00de0e2
(cherry picked from commit 5d32e628450494b72473c039c7d6f6ce57540bb1)
Diffstat (limited to 'libs/jpegrecoverymap/jpegencoderhelper.cpp')
0 files changed, 0 insertions, 0 deletions