Description
Update static data end address for skip/back reporting.
This callback should probably not be removed if skip/back reporting is enabled and output is organized by address. Removing it could cause other object types to loose track of where we are in the address space and thus make incorrect skip/back reports.
Definition at line 629 of file AsmUnparser.h.
#include <backend/asmUnparser/AsmUnparser.h>
Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackEnd:
Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackEnd:
Public Member Functions | |
| virtual bool | operator() (bool enabled, const StaticDataArgs &args) |
| Default callbacks. | |
 Public Member Functions inherited from Rose::BinaryAnalysis::AsmUnparser::UnparserCallback | |
| virtual bool | operator() (bool, const InsnArgs &) |
| Default callbacks. | |
| virtual bool | operator() (bool, const BasicBlockArgs &) |
| 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:
