| Home >> All >> org >> apache >> bcel >> verifier >> [ structurals Javadoc ] |
• org.apache.bcel.verifier.structurals: Javadoc index of package org.apache.bcel.verifier.structurals.
Package Samples:
• org.apache.bcel.verifier.structurals: BCEL's verifier JustIce is there to help you dump correct Java class files created or modified with BCEL.
Classes:
• ExecutionVisitor: This Visitor class may be used for a type-based Java Virtual Machine simulation. It does not check for correct types on the OperandStack or in the LocalVariables; nor does it check their sizes are sufficiently big. Thus, to use this Visitor for bytecode verifying, you have to make sure externally that the type constraints of the Java Virtual Machine instructions are satisfied. An InstConstraintVisitor may be used for this. Anyway, this Visitor does not mandate it. For example, when you visitIADD(IADD o), then there are two stack slots popped and one stack slot containing a Type.INT is pushed (where ...
• Subroutines: Instances of this class contain information about the subroutines found in a code array of a method. This implementation considers the top-level (the instructions reachable without a JSR or JSR_W starting off from the first instruction in a code array of a method) being a special subroutine; see getTopLevel() for that. Please note that the definition of subroutines in the Java Virtual Machine Specification, Second Edition is somewhat incomplete. Therefore, JustIce uses an own, more rigid notion. Basically, a subroutine is a piece of code that starts at the target of a JSR of JSR_W instruction and ...
• InstConstraintVisitor: A Visitor class testing for valid preconditions of JVM instructions. The instance of this class will throw a StructuralCodeConstraintException instance if an instruction is visitXXX()ed which has preconditions that are not satisfied. TODO: Currently, the JVM's behaviour concerning monitors (MONITORENTER, MONITOREXIT) is not modeled in JustIce.
• Pass3bVerifier: This PassVerifier verifies a method of class file according to pass 3, so-called structural verification as described in The Java Virtual Machine Specification, 2nd edition. More detailed information is to be found at the do_verify() method's documentation.
• GenericArray: A placeholder class that can be used to create an ObjectType of which has some of the properties arrays have. They implement java.lang.Cloneable and java.io.Serializable and they extend java.lang.Object.
• ExceptionHandler: This class represents an exception handler; that is, an ObjectType representing a subclass of java.lang.Throwable and the instruction the handler starts off (represented by an InstructionContext).
• OperandStack: This class implements a stack used for symbolic JVM stack simulation. [It's used an an operand stack substitute.] Elements of this stack are org.apache.bcel.generic.Type objects.
• Subroutine: This interface defines properties of JVM bytecode subroutines. Note that it is 'abused' to maintain the top-level code in a consistent fashion, too.
• UninitializedObjectType: This class represents an uninitialized object type; see The Java Virtual Machine Specification, Second Edition, page 147: 4.9.4 for more details.
• Frame: This class represents a JVM execution frame; that means, a local variable array and an operand stack.
• InstructionContext: An InstructionContext offers convenient access to information like control flow successors and such.
• LocalVariables: This class implements an array of local variables used for symbolic JVM simulation.
• ExceptionHandlers: This class allows easy access to ExceptionHandler objects.
• ControlFlowGraph: This class represents a control flow graph of a method.
| Home | Contact Us | Privacy Policy | Terms of Service |