Home | History | Annotate | Download | only in docs

Lines Matching full:verifier

3 <title>Dalvik Bytecode Verifier Notes</title>
7 <h1>Dalvik Bytecode Verifier Notes</h1>
10 The bytecode verifier in the Dalvik VM attempts to provide the same sorts
33 error cases because the verifier guarantees that they are impossible.
54 <h2>Verifier Differences</h2>
57 There are a few checks that the Dalvik bytecode verifier does not perform,
77 uninitialized objects to slip past the verifier -- without unduly
97 The Dalvik verifier is more restrictive than other VMs in one area:
110 completes normally or abnormally. The bytecode verifier optionally
114 The verifier uses a fairly simple-minded model. If you enter a monitor
116 subsequently-made copies of register N. The verifier does not attempt
120 will be the same reference, but the verifier doesn't recognize this).
128 This means that there are a number of situations in which the verifier
143 The verifier may reject a class immediately, or it may defer throwing
190 In early versions of Dalvik (as found in Android 1.6 and earlier), the verifier
200 class that didn't pass pre-verification, the verifier is invoked. If a