Searched refs:examine (Results 1 – 25 of 79) sorted by relevance
1234
| /external/zlib/src/examples/ |
| D | enough.c | 322 local void examine(int syms, int len, int left, int mem, int rem) in examine() function
385 examine(syms - use, len + 1, (left - use) << 1, in examine()
423 examine(n, root + 1, left, 1 << root, 0); in enough()
428 examine((n - left) << 1, root + 1, (n - left) << 1, in enough()
|
| /external/selinux/policycoreutils/sepolicy/sepolicy/help/ |
| D | lockdown_ptrace.txt | 6 Most people do not realize that any program they run can examine the memory of any other process ru…
|
| /external/sepolicy/ |
| D | perfprofd.te | 39 # simpleperf needs to examine /proc to collect task/thread info
|
| /external/strace/qemu_multiarch_testing/ |
| D | README | 21 There is no automated detection of errors for now: you need to examine
|
| /external/iptables/extensions/ |
| D | libxt_tcp.man | 22 flags which we should examine, written as a comma-separated list, and
|
| /external/valgrind/ |
| D | README_DEVELOPERS | 180 to examine the state of Outer.
182 examine the state of Inner.
184 examine the state of prog.
|
| /external/libvpx/libvpx/ |
| D | usage_dx.dox | 33 examine the rectangles that describe what data is valid to access and what
|
| D | usage.dox | 43 implementations. Applications \ref MUSTNOT attempt to examine or override
|
| /external/e2fsprogs/ |
| D | e2fsprogs.spec.in | 23 (used to examine the internal structure of a filesystem, to manually
|
| /external/mesa3d/docs/ |
| D | RELNOTES-3.5 | 135 flag. Drivers should instead examine the LogicOp state themselves
|
| /external/valgrind/docs/internals/ |
| D | segments-seginfos.txt | 95 > page just to examine the header)
|
| D | xml-output.txt | 34 all the way to the end, then examine output) and interactive GUIs
|
| /external/valgrind/gdbserver_tests/ |
| D | README_DEVELOPERS | 68 You can examine what is happening by enabling the trace
|
| /external/zlib/src/doc/ |
| D | rfc1952.txt | 472 values. It must examine FEXTRA/XLEN, FNAME, FCOMMENT and FHCRC
474 present. It need not examine any other part of the header or
|
| /external/llvm/docs/ |
| D | MCJITDesignAndImplementation.rst | 104 processRelocationRef method, which will examine the relocation and store
|
| D | TestingGuide.rst | 238 using them only to run tools that generate textual output you can then examine.
239 The recommended way to examine output to figure out if the test passes is using
|
| /external/llvm/docs/CommandGuide/ |
| D | llvm-cov.rst | 76 for each main source file where you want to examine the coverage results. This
|
| /external/flac/libFLAC/ppc/gas/ |
| D | lpc_asm.s | 59 # the branch mechanism may prevent dynamic loading; I still need to examine
|
| /external/flac/libFLAC/ppc/as/ |
| D | lpc_asm.s | 57 ; the branch mechanism may prevent dynamic loading; I still need to examine
|
| /external/lldb/docs/testsuite/ |
| D | a-detailed-walkthrough.txt | 211 pass this assertion, it's time to examine the contents of the file to make sure
|
| /external/antlr/antlr-3.4/runtime/ActionScript/project/src/org/antlr/runtime/ |
| D | TokenRewriteStream.as | 289 * First we need to examine replaces. For any replace op:
|
| /external/antlr/antlr-3.4/runtime/ObjC/Framework/ |
| D | ANTLRTokenRewriteStream.m | 532 * First we need to examine replaces. For any replace op:
|
| /external/clang/docs/ |
| D | LibASTMatchersTutorial.rst | 191 For example, suppose you wanted to examine only binary operators. There
|
| /external/iputils/doc/ |
| D | ping.sgml | 536 You can then examine this file for repeated patterns that you can test
|
| /external/elfutils/src/libelf/ |
| D | ChangeLog | 434 * note_xlate.h (elf_cvt_note): Don't examine a size too small to
|
1234