diff options
| author | Rusty Wagner <rusty@vector35.com> | 2019-02-15 15:31:24 -0500 |
|---|---|---|
| committer | Rusty Wagner <rusty@vector35.com> | 2019-02-15 15:31:24 -0500 |
| commit | 7bf7ef581aa8a572370a9929a1425c3d8d72a40d (patch) | |
| tree | 2ac619786e76566a2c7864b97a1e96fe1e759cbd /docs/dev | |
| parent | bd276c7886856f8813d392a8a72852a1a48b29f7 (diff) | |
Fix docs on newer mkdocs versions
Diffstat (limited to 'docs/dev')
| -rw-r--r-- | docs/dev/bnil-llil.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/dev/bnil-llil.md b/docs/dev/bnil-llil.md index 95c53bd8..9fc113d2 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 let's 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 |