The most important is to enable debug logging as suggested in the previous section. While third party plugins are not officially supported, there are a number of troubleshooting tips that can help identify the cause. Related, there is another setting: BN_DISABLE_USER_SETTINGS that will launch BN without relying on any user settings which is useful for identifying whether a particular behavior is the result of a setting without having to manually change a number of settings. In addition to the above mentioned method of disabling user-plugins, you can also set the environment variable BN_DISABLE_USER_PLUGINS (the value doesn't matter, the mere existence of the variable is enough).

Note that repository plugins are currently not disabled with this switch. Simply launch the process with the extra command-line option -p to disable all user plugins at load time. (note that both long and short-form of the command-line arguments are demonstrated in the above examples) Troubleshooting Plugins ¶ Disabling Plugins ¶ĭisabling plugins can be a quick way to diagnose whether some unexpected behavior is caused by Binary Ninja itself or a plugin.

Binary Ninja 3.3.3996 for ipod instal