Description
Functor to emit data block separation in output organized by address.
This does nothing if the output is organized by AST since the data block callbacks handle it in that case.
Definition at line 544 of file AsmUnparser.h.
#include <backend/asmUnparser/AsmUnparser.h>
Inheritance diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataBlockSeparation:
Collaboration diagram for Rose::BinaryAnalysis::AsmUnparser::StaticDataBlockSeparation:
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, const InsnArgs &) |
| Default callbacks. More... | |
| virtual bool | operator() (bool, const BasicBlockArgs &) |
| Default callbacks. More... | |
| virtual bool | operator() (bool, const DataBlockArgs &) |
| Default callbacks. More... | |
| virtual bool | operator() (bool, const FunctionArgs &) |
| Default callbacks. More... | |
| virtual bool | operator() (bool, const InterpretationArgs &) |
| Default callbacks. More... | |
Public Attributes | |
| SgAsmBlock * | prev_block |
Member Function Documentation
|
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:
