From 25f5c6d28c1bf5183d1ee1bfd791bf91ada11e9c Mon Sep 17 00:00:00 2001 From: Kharos102 Date: Fri, 3 Feb 2023 11:41:37 -0800 Subject: Fix typo in settings.md Small typo stuck in my mind --- docs/guide/settings.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/guide') 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`]|analysis.outlining.builtins| +|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`]|analysis.outlining.builtins| |analysis|Autorun Function Signature Matcher|Automatically run the function signature matcher when opening a binary for analysis.|`boolean`|`True`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|analysis.signatureMatcher.autorun| |analysis|Auto Function Analysis Suppression|Enable suppressing analysis of automatically discovered functions.|`boolean`|`False`|[`SettingsProjectScope`, `SettingsUserScope`, `SettingsResourceScope`]|analysis.suppressNewAutoFunctionAnalysis| |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`]|analysis.tailCallHeuristics| @@ -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`]|workflows.moduleWorkflow| -| | | |`enum`|`core.module.defaultAnalysis`| | | \ No newline at end of file +| | | |`enum`|`core.module.defaultAnalysis`| | | -- cgit v1.3.1