Packages

  • package root
    Definition Classes
    root
  • package org
    Definition Classes
    root
  • package opalj

    OPAL is a Scala-based framework for the static analysis, manipulation and creation of Java bytecode.

    OPAL is a Scala-based framework for the static analysis, manipulation and creation of Java bytecode. OPAL is designed with performance, scalability and adaptability in mind.

    Its main components are:

    • a library (Common) which provides generally useful data-structures and algorithms for static analyses.
    • a framework for implementing lattice based static analyses (Static Analysis Infrastructure)
    • a framework for parsing Java bytecode (Bytecode Infrastructure) that can be used to create arbitrary representations.
    • a library to create a one-to-one in-memory representation of Java bytecode (Bytecode Disassembler).
    • a library to create a representation of Java bytecode that facilitates writing simple static analyses (Bytecode Representation - org.opalj.br).
    • a scalable, easily customizable framework for the abstract interpretation of Java bytecode (Abstract Interpretation Framework - org.opalj.ai).
    • a library to extract dependencies between code elements and to facilitate checking architecture definitions.
    • a library for the lightweight manipulation and creation of Java bytecode (Bytecode Assembler).

    General Design Decisions

    Thread Safety

    Unless explicitly noted, OPAL is thread safe. I.e., the classes defined by OPAL can be considered to be thread safe unless otherwise stated. (For example, it is possible to read and process class files concurrently without explicit synchronization on the client side.)

    No null Values

    Unless explicitly noted, OPAL does not null values I.e., fields that are accessible will never contain null values and methods will never return null. If a method accepts null as a value for a parameter or returns a null value it is always explicitly documented. In general, the behavior of methods that are passed null values is undefined unless explicitly documented.

    No Typecasts for Collections

    For efficiency reasons, OPAL sometimes uses mutable data-structures internally. After construction time, these data-structures are generally represented using their generic interfaces (e.g., scala.collection.{Set,Map}). However, a downcast (e.g., to add/remove elements) is always forbidden as it would effectively prevent thread-safety.

    Assertions

    OPAL makes heavy use of Scala's Assertion Facility to facilitate writing correct code. Hence, for production builds (after thorough testing(!)) it is highly recommend to build OPAL again using -Xdisable-assertions.

    Definition Classes
    org
  • package tac

    Common definitions related to the definition and processing of three address code.

    Common definitions related to the definition and processing of three address code.

    Definition Classes
    opalj
  • package fpcf
    Definition Classes
    tac
  • package analyses
    Definition Classes
    fpcf
  • package cg
    Definition Classes
    analyses
  • package reflection
    Definition Classes
    cg
  • package rta
    Definition Classes
    cg
  • package xta

    Definition Classes
    cg
  • ArrayInstantiationsAnalysis
  • ArrayInstantiationsAnalysisScheduler
  • CTASetEntitySelector
  • ExternalField
  • ExternalWorld
  • FTASetEntitySelector
  • InstantiatedTypesAnalysis
  • InstantiatedTypesAnalysisScheduler
  • LibraryInstantiatedTypesBasedEntryPointsAnalysis
  • MTASetEntitySelector
  • TypePropagationAnalysis
  • TypePropagationAnalysisScheduler
  • TypePropagationState
  • TypePropagationTrace
  • TypeSetEntitySelector
  • XTASetEntitySelector

package xta

Source
package.scala
Linear Supertypes
AnyRef, Any
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. xta
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. Protected

Type Members

  1. final class ArrayInstantiationsAnalysis extends ReachableMethodAnalysis

    Updates InstantiatedTypes attached to a method's set for each array allocation occurring within that method.

    Updates InstantiatedTypes attached to a method's set for each array allocation occurring within that method.

    It also updates InstantiatedTypes of multidimensional ArrayTypes (see comments below for more details).

    The analysis is triggered for a method once it becomes reachable, i.e., a caller has been added. Thus, there are no property computations for unreachable methods.

  2. class ArrayInstantiationsAnalysisScheduler extends BasicFPCFTriggeredAnalysisScheduler
  3. case class ExternalField(declaringClass: ObjectType, name: String, declaredFieldType: FieldType) extends Product with Serializable

    Represents a field in the external world.

    Represents a field in the external world. Such fields can either not be resolved by the Project (because the class file defining the field was not loaded), or they belong to a class file which was loaded as a library file.

    declaringClass

    Object type of the class which declares the field (is also in the external world).

    name

    Name of the field.

    declaredFieldType

    Type of the field.

  4. class InstantiatedTypesAnalysis extends FPCFAnalysis

    Marks types as instantiated if their constructor is invoked.

    Marks types as instantiated if their constructor is invoked. Constructors invoked by subclass constructors do not result in additional instantiated types. The analysis does not just looks for "new" instructions, in order to support reflection.

    This analysis is adapted from the RTA version. Instead of adding the instantiations to the type set of the Project, they are added to the type set of the calling method. Which entity the type is attached to depends on the call graph variant used.

    TODO: Refactor this and the rta version in order to provide a common base-class.

  5. class InstantiatedTypesAnalysisScheduler extends BasicFPCFTriggeredAnalysisScheduler
  6. class LibraryInstantiatedTypesBasedEntryPointsAnalysis extends FPCFAnalysis

    In a library analysis scenario, this analysis complements the call graph by marking public methods of instantiated types reachable by unknown callers from outside the library.

    In a library analysis scenario, this analysis complements the call graph by marking public methods of instantiated types reachable by unknown callers from outside the library.

    While for RTA, the single type set attached to the Project is known in advance, there are many entities with type sets and the concrete entities are unknown in advance. Thus, this analysis is triggered. Similarly, since a type can be added to more than one type set, already processed types are remembered globally so that they are not processed twice.

  7. final class TypePropagationAnalysis extends ReachableMethodAnalysis

    This analysis handles the type propagation of XTA, MTA, FTA and CTA call graph algorithms.

  8. final class TypePropagationAnalysisScheduler extends BasicFPCFTriggeredAnalysisScheduler
  9. final class TypePropagationState[ContextType <: Context] extends BaseAnalysisState with TACAIBasedAnalysisState[ContextType]

    Manages the state of each method analyzed by TypePropagationAnalysis.

  10. type TypeSetEntity = AnyRef

    Type alias for Entity/AnyRef for better code comprehension.

    Type alias for Entity/AnyRef for better code comprehension. Within the context of propagation-based call graph construction algorithms, each entity has a corresponding "set entity". The type set of an entity is attached to its set entity. The set entity may be itself, or some other entity. The set of a single set entity may be shared among multiple entities. The assignment of entity to set entity varies per algorithm. For example, in XTA, the set entity of a DefinedMethod is the DefinedMethod itself, but in CTA, the set entity is the method's class.

  11. trait TypeSetEntitySelector extends (Entity) => TypeSetEntity

    Selects the corresponding set entity for each entity.

    Selects the corresponding set entity for each entity.

    This function is the only aspect XTA, MTA, FTA and CTA are distinguished by.

Value Members

  1. object CTASetEntitySelector extends TypeSetEntitySelector

    CTA type propagation uses a single set for all methods and field in a class.

  2. object ExternalWorld

    Entity which is used for types flow from/to the "external world".

  3. object FTASetEntitySelector extends TypeSetEntitySelector

    FTA type propagation uses a separate set for each method and a single set for all fields in a class.

  4. object LibraryInstantiatedTypesBasedEntryPointsAnalysis extends BasicFPCFTriggeredAnalysisScheduler
  5. object MTASetEntitySelector extends TypeSetEntitySelector

    MTA type propagation uses a separate set each field and a single set for all methods in a class.

  6. object TypePropagationTrace
  7. object XTASetEntitySelector extends TypeSetEntitySelector

    XTA type propagation uses a separate set for each method and each field.

Inherited from AnyRef

Inherited from Any

Ungrouped