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 - org.opalj.bi) that can be used to create arbitrary representations.
    • a library to create a one-to-one in-memory representation of Java bytecode (Bytecode Disassembler - org.opalj.da).
    • a library to convert this representation to Java class files (Bytecode Creator - org.opalj.bc).
    • a library to create a representation of Java bytecode that facilitates writing simple static analyses (Bytecode Representation - org.opalj.br).
    • a library to create a stackless, three-address code representation of Java bytecode that facilitates writing complex static analyses (Three Address Code - org.opalj.tac).
    • 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 (Dependencies Extraction - org.opalj.de) and to facilitate checking architecture definitions (Architecture Validation - org.opalj.av).
    • a library for the lightweight manipulation and creation of Java bytecode (Bytecode Assembler - org.opalj.ba).
    • a library for parsing Android packages (APK - org.opalj.apk).
    • libraries for writing static analyses using the interprocedural finite distributive subset (IFDS - org.opalj.ifds) and interprocedural distributive environment (IDE - org.opal.ide) algorithms.

    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 string

    Definition Classes
    analyses
  • package l1
    Definition Classes
    string
  • package interpretation
    Definition Classes
    l1
  • L1FunctionCallInterpreter
  • L1InterpretationHandler
  • L1NonVirtualFunctionCallInterpreter
  • L1NonVirtualMethodCallInterpreter
  • L1StaticFunctionCallInterpreter
  • L1VirtualFunctionCallInterpreter
  • L1VirtualMethodCallInterpreter

package interpretation

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Type Members

  1. trait L1FunctionCallInterpreter extends AssignmentLikeBasedStringInterpreter with ParameterEvaluatingStringInterpreter

    Base trait for all function call interpreters on L1.

    Base trait for all function call interpreters on L1. Provides support for multiple possible called methods as well as adding called methods and return dependees at runtime.

  2. class L1InterpretationHandler extends L0InterpretationHandler

    <invalid inheritdoc annotation>

    <invalid inheritdoc annotation>

    Interprets statements similar to the org.opalj.tac.fpcf.analyses.string.l0.interpretation.L0InterpretationHandler but handles all sorts of function calls on top.

  3. case class L1NonVirtualFunctionCallInterpreter()(implicit p: SomeProject, ps: PropertyStore, highSoundness: Boolean) extends AssignmentLikeBasedStringInterpreter with L1FunctionCallInterpreter with Product with Serializable

    Processes NonVirtualFunctionCalls without a call graph.

  4. case class L1NonVirtualMethodCallInterpreter()(implicit highSoundness: Boolean) extends StringInterpreter with Product with Serializable

    Processes NonVirtualMethodCalls without a call graph.

    Processes NonVirtualMethodCalls without a call graph. Currently, only calls to <init> of strings, string buffers and string builders are interpreted. For other calls, ID is returned.

  5. case class L1StaticFunctionCallInterpreter()(implicit p: SomeProject, ps: PropertyStore, project: SomeProject, highSoundness: Boolean) extends AssignmentBasedStringInterpreter with L1ArbitraryStaticFunctionCallInterpreter with L1StringValueOfFunctionCallInterpreter with L1SystemPropertiesInterpreter with Product with Serializable

    Interprets some specific static calls in the context of their method as well as arbitrary static calls without a call graph.

    Interprets some specific static calls in the context of their method as well as arbitrary static calls without a call graph.

    See also

    L1ArbitraryStaticFunctionCallInterpreter, L1StringValueOfFunctionCallInterpreter, L1SystemPropertiesInterpreter

  6. class L1VirtualFunctionCallInterpreter extends AssignmentLikeBasedStringInterpreter with L1ArbitraryVirtualFunctionCallInterpreter with L1AppendCallInterpreter with L1SubstringCallInterpreter

    Processes VirtualFunctionCalls without a call graph.

    Processes VirtualFunctionCalls without a call graph. Some string operations such as append, toString or substring are either fully interpreted or approximated.

    Note

    Due to a missing call graph, arbitrary (i.e. not otherwise interpreted) virtual function calls will not be interpreted.

  7. class L1VirtualMethodCallInterpreter extends StringInterpreter

    Processes VirtualMethodCalls without a call graph.

    Processes VirtualMethodCalls without a call graph. Currently, only calls to setLength of string buffers and string builders are interpreted. For other calls, ID is returned.

Value Members

  1. object L1InterpretationHandler

Ungrouped