public interface

IFlowInformation

com.pnfsoftware.jeb.core.units.code.IFlowInformation
Known Indirect Subclasses

Class Overview

Information relative to flow change (break in the flow, indicating the end of a Basic Block).

Summary

Public Methods
abstract int getDelaySlotCount()
abstract List<IEntryPointDescription> getTargets()
Get the a list of targets.
abstract boolean isBroken()
Determine if this object does contain flow information.
abstract boolean isBrokenEmpty()
Determine if this object does contain flow information but has no known targets.
abstract boolean mustComputeFallThrough()
Indicate if the flow information includes a fall-through address (relative to the current instruction) that is not present in the fall-through object itself.

Public Methods

public abstract int getDelaySlotCount ()

public abstract List<IEntryPointDescription> getTargets ()

Get the a list of targets. Be careful, this list does not include the fall-through target if it is implied (eg, when flow-info is returned by getRoutineCall(long)) or when its calculation was requested dynamically (via mustComputeFallThrough()).

Returns
  • the list of addresses that must be checked, possibly empty. A null value signifies no-flow information.

public abstract boolean isBroken ()

Determine if this object does contain flow information.

Returns
  • true is the flow is broken (eg, generic branch)

public abstract boolean isBrokenEmpty ()

Determine if this object does contain flow information but has no known targets.

public abstract boolean mustComputeFallThrough ()

Indicate if the flow information includes a fall-through address (relative to the current instruction) that is not present in the fall-through object itself. If this method returns true, the caller must dynamically calculate the fall-through address itself.

Note that the creator of a flowinfo object may decide to add the fall-through (if any) in the flowinfo object target list. However, in some cases, such as branching instructions with delay slot(s), it is simpler to indicate that the branching instruction allows a fall-through flow, but that it should be computer by the client/user, instead of stored or computer by the flowinfo object.

Voluntarily broke JavaBeans convention: named `must` instead of `is`.