ret-sync | debugging session | Reverse Engineering library

For IDA installation, copy Syncplugin.py and retsync folder from ext_ida to IDA plugins directory, for example:.
C:\Program Files\IDA Pro 7.4\plugins
%APPDATA%\Hex-Rays\IDA Pro\plugins
~/.idapro/plugins
Either use the pre-built version from the ext_ghidra/dist folder or follow the instruction to build it. Each extension build only supports the version of Ghidra specified in the plugin's file name. E.g. ghidra_9.1_PUBLIC_20191104_retsync.zip is for Ghidra 9.1 Public.
Install Ghidra
Install gradle
Build extension for your Ghidra installation (replace $GHIDRA_DIR with your installation directory)
A status window is also available from Windows -> RetSyncPlugin. You generally want to drop it on the side to integrate it with the Ghidra environment windows.
From Ghidra projects manager: File -> Install Extensions..., click on the + sign and select the ext_ghidra/dist/ghidra_*_retsync.zip and click OK. This will effectively extract the retsync folder from the zip into $GHIDRA_DIR/Extensions/Ghidra/
Restart Ghidra as requested
After reloading Ghidra, open a module in CodeBrowser. It should tell you a new extension plugin has been detected. Select "yes" to configure it. Then tick "RetSyncPlugin" and click OK. The console should show something like:
From Ghidra CodeBrowser tool: use toolbar icons or shortcuts to enable (Alt+s)/disable (Alt+Shift+s)/restart (Alt+r) synchronization.
ret-sync is not yet distributed through the Binary Ninja's Plugin Manager; a manual installation is required. Simply copy that content of the ext_bn folder into Binary Ninja's plugins folder, for example:.
Either use pre-built binaries or use the Visual Studio 2017 solution provided in ext_windbg, (see https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes if needed). This will build the x64\release\sync.dll file.
You will need to copy the resulting sync.dll file into the appropriate Windbg extension path. For earlier versions of Windbg this is is something like this (be careful of x86/x64 flavours), for example. The folder for storing extension seems to be based on the PATH, so you need to put it one of the queried locations.
WinDbg Classic:
Windbg Preview
Note: If you get the following error, it is because you haven't copied the file to the right folder in the above steps. The error below usually means that Windbg tried to load the incorrect flavour of the extension, ex: x86 in place of the x64 sync.dll.
LLDB support is experimental, however:.
Load extension (can also be added in ~/.lldbinit)
OllyDbg 1.10 support is experimental, however:.
Build the plugin using the VS solution (optional, see pre-built binaries)
Copy the dll within OllyDbg's plugin directory
OllyDbg2 support is experimental, however:.
Build the plugin using the VS solution (optional, see pre-built binaries)
Copy the dll within OllyDbg2's plugin directory
Based on testplugin, https://github.com/x64dbg/testplugin. x64dbg support is experimental, however:.
Build the plugin using the VS solution (optional, see pre-built binaries). May you need a different version of the plugin sdk, a copy can be found in each release of x64dbg. Paste the "pluginsdk" directory into "ext_x64dbg\x64dbg_sync"
Copy the dll (extension is .d32 or .dp64) within x64dbg's plugin directory.