Description
Functor to print skip/back information when an instruction 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 instructions but leave it in place for static data).
Definition at line 373 of file AsmUnparser.h.
#include <backend/asmUnparser/AsmUnparser.h>
Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::InsnSkipBackBegin:
Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::InsnSkipBackBegin:
Public Member Functions | |
| virtual bool | operator() (bool enabled, const InsnArgs &args) |
| Default callbacks. | |
 Public Member Functions inherited from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback | |
| virtual bool | operator() (bool, const BasicBlockArgs &) |
| Default callbacks. | |
| virtual bool | operator() (bool, const StaticDataArgs &) |
| Default callbacks. | |
| virtual bool | operator() (bool, const DataBlockArgs &) |
| Default callbacks. | |
| virtual bool | operator() (bool, const FunctionArgs &) |
| Default callbacks. | |
| virtual bool | operator() (bool, const InterpretationArgs &) |
| Default callbacks. | |
Member Function Documentation
◆ operator()()
|
virtual |
Default callbacks.
The default is to abort, because if these are called it means one of three things:
- The arguments are wrong in the subclass and the subclass therefore isn't providing an implementation when it thinks it is.
- The wrong type was used for the second argument. Instruction callbacks use InsnArgs, basic block callbacks use BasicBlockArgs, etc.
- 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:
