Description
Definition at line 280 of file AsmUnparser.h.
Classes | |
| struct | BasicBlockArgs |
| Arguments passed to basic block unparsing callbacks. More... | |
| struct | DataBlockArgs |
| Arguments passed to data block unparsing callbacks. More... | |
| struct | FunctionArgs |
| Arguments passed to function unparsing callbacks. More... | |
| struct | GeneralArgs |
| Arguments common to all unparser callback lists. More... | |
| struct | InsnArgs |
| Arguments passed to instruction unparsing callbacks. More... | |
| struct | InterpretationArgs |
| Arguments passed to interpretation unparsing callbacks. More... | |
| struct | StaticDataArgs |
| Arguments passed to data unparsing callbacks. More... | |
Public Member Functions | |
| virtual bool | operator() (bool, const InsnArgs &) |
| Default callbacks. | |
| 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. | |
Constructor & Destructor Documentation
◆ ~UnparserCallback()
|
inlinevirtual |
Definition at line 344 of file AsmUnparser.h.
Member Function Documentation
◆ operator()() [1/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::InsnSkipBackBegin, Rose::BinaryAnalysis::AsmUnparser::InsnBlockSeparation, Rose::BinaryAnalysis::AsmUnparser::InsnFuncEntry, Rose::BinaryAnalysis::AsmUnparser::InsnAddress, Rose::BinaryAnalysis::AsmUnparser::InsnRawBytes, Rose::BinaryAnalysis::AsmUnparser::InsnBlockEntry, Rose::BinaryAnalysis::AsmUnparser::InsnStackDelta, Rose::BinaryAnalysis::AsmUnparser::InsnBody, Rose::BinaryAnalysis::AsmUnparser::InsnNoEffect, Rose::BinaryAnalysis::AsmUnparser::InsnComment, Rose::BinaryAnalysis::AsmUnparser::InsnLineTermination, Rose::BinaryAnalysis::AsmUnparser::InsnSkipBackEnd, and Rose::BinaryAnalysis::AsmUnparser::StaticDataDisassembler::DataNote.
Definition at line 356 of file AsmUnparser.h.
◆ operator()() [2/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::BasicBlockReasons, Rose::BinaryAnalysis::AsmUnparser::BasicBlockPredecessors, Rose::BinaryAnalysis::AsmUnparser::BasicBlockNoopUpdater, Rose::BinaryAnalysis::AsmUnparser::BasicBlockNoopWarning, Rose::BinaryAnalysis::AsmUnparser::BasicBlockBody, Rose::BinaryAnalysis::AsmUnparser::BasicBlockOutgoingStackDelta, Rose::BinaryAnalysis::AsmUnparser::BasicBlockSuccessors, Rose::BinaryAnalysis::AsmUnparser::BasicBlockLineTermination, and Rose::BinaryAnalysis::AsmUnparser::BasicBlockCleanup.
Definition at line 357 of file AsmUnparser.h.
◆ operator()() [3/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackBegin, Rose::BinaryAnalysis::AsmUnparser::StaticDataBlockSeparation, Rose::BinaryAnalysis::AsmUnparser::StaticDataRawBytes, Rose::BinaryAnalysis::AsmUnparser::StaticDataBlockEntry, Rose::BinaryAnalysis::AsmUnparser::StaticDataDetails, Rose::BinaryAnalysis::AsmUnparser::StaticDataComment, Rose::BinaryAnalysis::AsmUnparser::StaticDataLineTermination, Rose::BinaryAnalysis::AsmUnparser::StaticDataDisassembler, Rose::BinaryAnalysis::AsmUnparser::StaticDataSkipBackEnd, and Rose::BinaryAnalysis::AsmUnparser::DataBlockTitle.
Definition at line 358 of file AsmUnparser.h.
◆ operator()() [4/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::DataBlockBody, and Rose::BinaryAnalysis::AsmUnparser::DataBlockLineTermination.
Definition at line 359 of file AsmUnparser.h.
◆ operator()() [5/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::FunctionEntryAddress, Rose::BinaryAnalysis::AsmUnparser::FunctionSeparator, Rose::BinaryAnalysis::AsmUnparser::FunctionReasons, Rose::BinaryAnalysis::AsmUnparser::FunctionName, Rose::BinaryAnalysis::AsmUnparser::FunctionLineTermination, Rose::BinaryAnalysis::AsmUnparser::FunctionComment, Rose::BinaryAnalysis::AsmUnparser::FunctionPredecessors, Rose::BinaryAnalysis::AsmUnparser::FunctionSuccessors, Rose::BinaryAnalysis::AsmUnparser::FunctionAttributes, and Rose::BinaryAnalysis::AsmUnparser::FunctionBody.
Definition at line 360 of file AsmUnparser.h.
◆ operator()() [6/6]
|
inlinevirtual |
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 in Rose::BinaryAnalysis::AsmUnparser::InterpName, and Rose::BinaryAnalysis::AsmUnparser::InterpBody.
Definition at line 361 of file AsmUnparser.h.
The documentation for this class was generated from the following file:
