Lines Matching full:must
33 The magic number of the DEX file must be "dex\n035\0".
43 The checksum must be an Adler-32 checksum of the whole file contents
49 The signature must be a SHA-1 hash of the whole file contents except magic,
52 The file_size must match the actual file size in bytes.
54 The header_size must have the value 0x70.
56 The endian_tag must have either the value ENDIAN_CONSTANT or
60 and data sections, the offset and size fields must be either both zero or both
61 non-zero. In the latter case, the offset must be four-byte-aligned.
63 All offset fields in the header except map_off must be four-byte-aligned.
65 The map_off field must be either zero or point into the data section. In the
66 latter case, the data section must exist.
69 and data sections must overlap each other or the header.
71 If a map exists, then each map entry must have a valid type. Each type may
74 If a map exists, then each map entry must have a nonzero offset and size. The
75 offset must point into the corresponding section of the file (i.e. a
76 string_id_item must point into the string_ids section) and the explicit or
77 implicit size of the item must match the actual contents and size of the
80 If a map exists, then the offset of map entry n+1 must be greater or equal to
84 The following types of entries must have an offset that is
89 For each string_id_item, the string_data_off field must contain a valid
91 field must contain a valid MUTF-8 string, and the utf16_size must match the
94 For each type_id_item, the desciptor_idx field must contain a valid reference
95 into the string_ids list. The referenced string must be a valid type descriptor.
97 For each proto_id_item, the shorty_idx field must contain a valid reference
98 into the string_ids list. The referenced string must be a valid shorty descriptor.
99 Also, the return_type_idx field must be a valid index into the type_ids section,
100 and the parameters_off field must be either zero or a valid offset pointing
101 into the data section. If nonzero, the parameter list must not contain any void
104 For each field_id_item, both the class_idx and type_idx fields must be a valid
106 type_ids list. The entry referenced by class_idx must be a non-array reference type.
107 In addition, the name_idx field must be a valid reference into the string_ids
108 section, and the contents of the referenced entry must conform to the MemberName
111 For each method_id_item, the class_idx field must be a valid index into the
113 referenced entry must be a non-array reference type. The proto_id field must
114 be a valid reference into the proto_ids list. The name_idx field must be a
116 section, and the contents of the referenced entry must conform to the MemberName
121 For each field_id_item, the class_idx field must be a valid index into the
122 type_ids list. The referenced entry must be a non-array reference type.
159 The <code>insns</code> array must not be empty.
173 The first opcode in the <code>insns</code> array must have index zero.
187 The <code>insns</code> array must only contain valid Dalvik opcodes.
201 The index of instruction <code>n+1</code> must equal the index of
217 The last instruction in the <code>insns</code> array must end at index
232 All <code>goto</code> and <code>if-<kind></code> targets must
247 All targets of a <code>packed-switch</code> instruction must be
249 must be consistent.
263 All targets of a <code>sparse-switch</code> instruction must be
264 opcodes within in the same method. The corresponding table must be
280 <code>const-string/jumbo</code> instructions must be a valid index
296 <code>iput<kind></code> instructions must be a valid index into
297 the field constant pool. The referenced entry must represent an
313 <code>sput<kind></code> instructions must be a valid index into
314 the field constant pool. The referenced entry must represent a static
331 <code>invoke-static</code> instructions must be a valid index into the
333 <code>method_id</code> must belong to a class (not an interface).
349 <code>invoke-static/range</code> instructions must be a valid index
351 <code>method_id</code> must belong to a class (not an interface).
365 A method the name of which starts with a '<' must only be invoked
383 instruction must be a valid index into the method constant pool. The
384 referenced <code>method_id</code> must belong to an interface (not a
400 instruction must be a valid index into the method constant pool.
401 The referenced <code>method_id</code> must belong to an interface (not
418 <code>filled-new-array/range</code> instructions must be a valid index
435 instructions must be a valid index into the type constant pool.
450 instruction must be less than <code>256</code>.
464 The <code>new</code> instruction must not refer to array classes,
479 The type referred to by a <code>new-array</code> instruction must be
495 (non-pair) fashion must be valid for the current method. That is,
496 their indices must be non-negative and smaller than
512 fashion must be valid for the current method. That is, their indices
513 must be non-negative and smaller than <code>registers_size-1</code>.
554 must always match the instruction.
568 Register pairs must never be broken up.
597 An <code>invoke-direct</code> instruction must only invoke an instance
613 An instance initializer must only be invoked on an uninitialized
644 instruction must not be used if the same
660 An instance initializer must call another instance initializer (same
678 All actual method arguments must be assignment-compatible with their
693 For each instance method invocation, the actual instance must be
709 A <code>return<kind></code> instruction must match its
725 the instance being accessed must be either the current class or one
740 The type of a value stored into a static field must be
755 The type of a value stored into a field must be assignment-compatible
770 The type of every value stored into an array must be
785 The <code>A</code> operand of a <code>throw</code> instruction must
800 The last reachable instruction of a method must either be a backwards
802 <code>throw</code> instruction. It must not be possible to leave the
833 A <code>move-result<kind></code> instruction must be immediately
851 A <code>move-result<kind></code> instruction must be immediately
853 <code>return-<kind></code> instruction (it must not be jumped
870 A <code>move-exception</code> instruction must only appear as the
886 and <code>fill-array-data</code> pseudo-instructions must not be
