@ParametersAreNonnullByDefault @AnalysisContextContained

Package edu.umd.cs.findbugs.ba.obl

Implementation of dataflow analysis for checking whether obligations to close streams and other resources (e.g.

See: Description

Interface Summary

Interface	Description
ObligationPolicyDatabaseEntry	Interface defining an entry in the ObligationPolicyDatabase.

Class Summary

Class	Description
InstructionActionCache	A cache for looking up the collection of ObligationPolicyDatabaseActions associated with a given InstructionHandle.
MatchMethodEntry	An ObligationPolicyDatabaseEntry which creates or deletes an obligation based on a call to a specified method.
Obligation	An obligation that must be cleaned up by error handling code.
ObligationAnalysis	Dataflow analysis to track obligations (i/o streams and other resources which must be closed).
ObligationDataflow	Dataflow class for ObligationAnalysis.
ObligationFactory	Factory for Obligation and ObligationSet objects to be used in an instance of ObligationAnalysis.
ObligationPolicyDatabase	Policy database which defines which methods create and remove obligations.
ObligationPolicyDatabaseAction	An action applied by an entry in the ObligationPolicyDatabase.
ObligationSet	A multiset of obligations that must be cleaned up by error-handling code.
State	Error-handling obligation analysis state.
StateSet	A dataflow fact used in ObligationAnalysis.

Enum Summary

Enum	Description
ObligationPolicyDatabaseActionType	Enumeration describing possible actions for policy database entries.
ObligationPolicyDatabaseEntryType	Types of ObligationPolicyDatabaseEntries.

Exception Summary

Exception	Description
NonexistentObligationException
ObligationAcquiredOrReleasedInLoopException	Exception to indicate that ObligationAnalysis has detected a situation in which an obligation is either acquired or released inside a loop.

Package edu.umd.cs.findbugs.ba.obl Description

Implementation of dataflow analysis for checking whether obligations to close streams and other resources (e.g. database objects) are satisfied.

See Weimer and Necula, Finding and preventing run-time error handling mistakes.