diff options
Diffstat (limited to 'docs/guide')
| -rw-r--r-- | docs/guide/settings.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/guide/settings.md b/docs/guide/settings.md index 327ed53a..457dd54b 100644 --- a/docs/guide/settings.md +++ b/docs/guide/settings.md @@ -83,7 +83,7 @@ All settings are uniquely identified with an identifier string. Identifiers are | | | enum: Perform fast initial analysis of the binary. This mode does not analyze types or data flow through stack variables. [LLIL and Equivalents]|`enum`|`basic`| | | | | | enum: Perform analysis which includes type propagation and data flow. [MLIL and Equivalents]|`enum`|`intermediate`| | | | | | enum: Perform full analysis of the binary.|`enum`|`full`| | | -|analysis|Builtin Outlining for Constant Expressions|Enable outlinging for constant expression compiler emitted builtins. This feature is under active development. Therefore, disabled by default.|`boolean`|`False`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='analysis.outlining.builtins'>analysis.outlining.builtins</a>| +|analysis|Builtin Outlining for Constant Expressions|Enable outlining for constant expression compiler emitted builtins. This feature is under active development. Therefore, disabled by default.|`boolean`|`False`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='analysis.outlining.builtins'>analysis.outlining.builtins</a>| |analysis|Autorun Function Signature Matcher|Automatically run the function signature matcher when opening a binary for analysis.|`boolean`|`True`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='analysis.signatureMatcher.autorun'>analysis.signatureMatcher.autorun</a>| |analysis|Auto Function Analysis Suppression|Enable suppressing analysis of automatically discovered functions.|`boolean`|`False`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='analysis.suppressNewAutoFunctionAnalysis'>analysis.suppressNewAutoFunctionAnalysis</a>| |analysis|Tail Call Heuristics|Attempts to recover function starts that may be obscured by tail call optimization (TCO). Specifically, branch targets within a function are analyzed as potential function starts.|`boolean`|`True`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='analysis.tailCallHeuristics'>analysis.tailCallHeuristics</a>| @@ -380,4 +380,4 @@ All settings are uniquely identified with an identifier string. Identifiers are | | | |`enum`|`core.function.objectiveC`| | | | | | |`enum`|`core.module.defaultAnalysis`| | | |workflows|Module Workflow|Workflow selection for module-based analysis. Note: Module-based workflows incomplete.|`string`|`core.module.defaultAnalysis`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|<a id='workflows.moduleWorkflow'>workflows.moduleWorkflow</a>| -| | | |`enum`|`core.module.defaultAnalysis`| | |
\ No newline at end of file +| | | |`enum`|`core.module.defaultAnalysis`| | | |