ROSE  0.9.9.149
Public Member Functions | List of all members
Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackBegin Class Reference

Description

Functor to print skip/back information when a static data block is entered.

Skip/back information can be enabled/disabled across the entire unparser by calling the set_skipback_reporting() method. This callback can be removed per object type without confusing other objects that define a similar callbacks (for example, to disable skip/back reporting for static data blocks but leave it in place for instructions).

Definition at line 530 of file AsmUnparser.h.

#include <AsmUnparser.h>

Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackBegin:
Inheritance graph
[legend]
Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackBegin:
Collaboration graph
[legend]

Public Member Functions

virtual bool operator() (bool enabled, const StaticDataArgs &args)
 Default callbacks. More...
 
- Public Member Functions inherited from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback
virtual bool operator() (bool enabled, const InsnArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool enabled, const BasicBlockArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool enabled, const DataBlockArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool enabled, const FunctionArgs &)
 Default callbacks. More...
 
virtual bool operator() (bool enabled, const InterpretationArgs &)
 Default callbacks. More...
 

Member Function Documentation

virtual bool Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackBegin::operator() ( bool  enabled,
const StaticDataArgs  
)
virtual

Default callbacks.

The default is to abort, because if these are called it means one of three things:

  1. The arguments are wrong in the subclass and the subclass therefore isn't providing an implementation when it thinks it is.
  2. The wrong type was used for the second argument. Instruction callbacks use InsnArgs, basic block callbacks use BasicBlockArgs, etc.
  3. The functor was added to the wrong callback list. For instance, an instruction functor was accidently added to one of the function callback lists.

Reimplemented from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback.


The documentation for this class was generated from the following file: