diff options
Diffstat (limited to 'docs/dev')
| -rw-r--r-- | docs/dev/bnil-llil.md | 6 | ||||
| -rw-r--r-- | docs/dev/documentation.md | 2 |
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/dev/bnil-llil.md b/docs/dev/bnil-llil.md index 7748d140..71cedd96 100644 --- a/docs/dev/bnil-llil.md +++ b/docs/dev/bnil-llil.md @@ -2,7 +2,7 @@ The Binary Ninja Intermediate Language (BNIL) is a semantic representation of the assembly language instructions for a native architecture in Binary Ninja. BNIL is actually a family of intermediate languages that work together to provide functionality at different abstraction layers. This developer guide is intended to cover some of the mechanics of the LLIL to distinguish it from the other ILs in the BNIL family. - + The Lifted IL is very similar to the LLIL and is primarily of interest for Architecture plugin authors. If you're writing an analysis plugin, you'll always want to be working at LLIL or higher. During each stage of the lifting process a number of transformations take place, and each layer of IL can have different instructions. Because of this, you can not rely on an instruction from one layer existing in another. @@ -10,7 +10,7 @@ The Lifted IL is very similar to the LLIL and is primarily of interest for Archi Since doing is the easiest way to learn lets start with a simple example binary and step through analyzing it using the python console. - + - Download [chal1](../files/chal1) and open it with Binary Ninja - Next, bring up the `Low Level IL` view by clicking in the options pane at the bottom of the screen @@ -143,7 +143,7 @@ Now with some knowledge of the `LowLevelIL` class lets try to do something with ``` >>> for block in current_function.low_level_il: ... for instr in block: -... if instr.operation == LowLevelILOperation.LLIL_SET_REG and instr.dest == 'rdx': +... if instr.operation == LowLevelILOperation.LLIL_SET_REG and instr.dest.name == 'rdx': ... print instr.address, instr.instr_index, instr ... 4196490 14 rdx = [rax].q diff --git a/docs/dev/documentation.md b/docs/dev/documentation.md index 830bd4ec..16a1c9ee 100644 --- a/docs/dev/documentation.md +++ b/docs/dev/documentation.md @@ -27,7 +27,7 @@ To contribute to the Binary Ninja documentation, first sign the [contribution li Changing documentation for the API itself is fairly straight forward. Use [doxygen style comment blocks](https://www.stack.nl/~dimitri/doxygen/manual/docblocks.html) in C++ and C, and [restructured text blocks](http://thomas-cokelaer.info/tutorials/sphinx/docstring_python.html) for python for the source. The user documentation is located in the `api/docs/` folder and the API documentation is generated from the config in the `api/api-docs` folder. !!! Tip "Tip" - When updating user documentation, the `mkdoc serve` feature is particularly helpful. + When updating user documentation, the `mkdocs serve` feature is particularly helpful. [contribution license agreement]: https://binary.ninja/cla.pdf [Vector 35]: https://vector35.com/ |