summaryrefslogtreecommitdiff
path: root/docs/guide/troubleshooting.md
diff options
context:
space:
mode:
authorJordan Wiens <github@psifertex.com>2019-07-22 17:49:03 -0400
committerJordan Wiens <github@psifertex.com>2019-07-22 17:49:03 -0400
commitd4fa2fa1d657ced48dd00d64d44dcc2cd621ae01 (patch)
treeaa88057388d147865bcb66554c3104a39490b37f /docs/guide/troubleshooting.md
parent0736fc2a1f9590c110bf0add9c7651ac4e6e8919 (diff)
allow launching without loading user plugins
Diffstat (limited to 'docs/guide/troubleshooting.md')
-rw-r--r--docs/guide/troubleshooting.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md
index 0c43bd25..c14feef5 100644
--- a/docs/guide/troubleshooting.md
+++ b/docs/guide/troubleshooting.md
@@ -22,6 +22,10 @@ Alternatively, it might be easier to save debug logs to a file instead:
(note that both long and short-form of the command-line arguments are demonstrated in the above examples)
+## Disabling Plugins
+
+Disabling plugins can be a quick way to diagnose whether some unexpected behavior is casued by Binary Ninja itself or a plugin. Simply launch the process with the extra command-lien option `-p` to disable all user plugins at load time.
+
## Plugin Troubleshooting
While third party plugins are not officially supported, there are a number of troubleshooting tips that can help identify the cause. The most important is to enable debug logging as suggested in the previous section. This will often highlight problems with python paths or any other issues that prevent plugins from running.