Home
last modified time | relevance | path

Searched refs:executable (Results 1 – 25 of 70) sorted by relevance

123

/system/extras/simpleperf/runtest/
Druntest.conf3 <executable name="simpleperf_runtest_one_function"/>
21 <executable name="simpleperf_runtest_two_functions"/>
43 <executable name="simpleperf_runtest_function_fork"/>
66 <executable name="simpleperf_runtest_function_pthread"/>
85 <executable name="simpleperf_runtest_comm_change"/>
109 <executable name="simpleperf_runtest_function_recursive"/>
157 <executable name="simpleperf_runtest_function_indirect_recursive"/>
198 <executable name="simpleperf_runtest_comm_change"/>
207 <executable name="simpleperf_runtest_run_and_sleep"/>
216 <executable name="simpleperf_runtest_run_and_sleep"/>
/system/sepolicy/private/
Dpreopt2cachename.te1 # preopt2cachename executable
3 # This executable translates names from the preopted versions the build system
Dmediatuner.te30 # mediatuner should never execute any executable without a
Dmediadrmserver.te32 # mediadrmserver should never execute any executable without a
Dmediaswcodec.te32 # mediaswcodec_server should never execute any executable without a
Dhal_cas.te38 # hal_cas should never execute any executable without a
Dhal_camera.te34 # hal_camera should never execute any executable without a
Dhal_audio.te38 # Should never execute any executable without a domain transition
Dmediametrics.te35 # mediametrics should never execute any executable without a
Dhal_configstore.te14 # Should never execute an executable without a domain transition
Dhal_drm.te59 # hal_drm should never execute any executable without a
Dhal_omx.te35 # hal_omx_server should never execute any executable without a
/system/unwinding/libunwindstack/
DAndroidVersions.md23 and one read/executable. The libunwindstack on P and the unwinder on older
32 that the bias is coming from the program header for the executable
53 in the executable. On API level 28, this would result in some incorrect
70 contains the executable code from the elf. Before this, the unwinder
72 contained the elf header data and the executable code.
106 executable PT\_LOAD program header. This has only ever been a problem
113 or eh\_frame\_hdr does not have the same bias as the executable section,
121 executable map for the elf data and executable data, the offset into the
131 a read-only map of the elf data, and a read-executable map of the
/system/update_engine/scripts/
Dota_stress_test.py38 python = sys.executable
73 python = sys.executable
DAndroid.bp18 // For module X, if we need to build it both as a library and an executable:
/system/vold/fs/
DVfat.h32 bool executable, int ownerUid, int ownerGid, int permMask, bool createLost);
DExt4.h32 bool executable);
DVfat.cpp133 bool executable, int ownerUid, int ownerGid, int permMask, bool createLost) { in Mount() argument
142 flags |= (executable ? 0 : MS_NOEXEC); in Mount()
DExt4.cpp125 bool executable) { in Mount() argument
134 flags |= (executable ? 0 : MS_NOEXEC); in Mount()
/system/extras/simpleperf/scripts/test/
Djava_app_test.py61 args = [sys.executable, TestHelper.script_path("app_profiler.py"),
76 args = [sys.executable, TestHelper.script_path('app_profiler.py'),
Dtest_utils.py96 args = [sys.executable, cls.script_path(
170 args = [sys.executable, TestHelper.script_path(args[0])] + args[1:]
/system/update_engine/
DAndroid.bp553 // update_engine (type: executable)
576 // update_engine_nostats (type: executable)
613 // update_engine_sideload (type: executable)
615 // A binary executable equivalent to update_engine daemon that installs an update
688 // update_engine_client (type: executable)
890 // delta_generator (type: executable)
932 // test_http_server (type: executable)
946 // test_subprocess (type: executable)
1101 // update_engine_unittests (type: executable)
1175 // update_engine_unittests (type: executable)
/system/sepolicy/vendor/
Dmediacodec.te31 # mediacodec should never execute any executable without a domain transition
/system/update_engine/stable/
DAndroid.bp66 // update_engine_stable_client (type: executable)
/system/bpfprogs/
DLICENSE129 Section 2) in object code or executable form under the terms of Sections 1 and
145 object code or executable form with such an offer, in accord with
149 modifications to it. For an executable work, complete source code means all
152 of the executable. However, as a special exception, the source code
155 of the operating system on which the executable runs, unless that component
156 itself accompanies the executable.
158 If distribution of executable or object code is made by offering access to copy
340 executable, regardless of the license terms of these independent modules,
341 and to copy and distribute the resulting executable under terms of your

123