Update readme for 0.7.0

Author: ubfx

Readme.md

@@ -5,11 +5,14 @@ Check out the [BinDiff manual](https://www.zynamics.com/bindiff/manual/) to see
 
 **Please report bugs via the issue feature on github**
 
-## What it does / Changelog
+## Changelog
+### v0.7.0 (Ghidra versions >= 11.4)
+* No changes except Ghidra version compatibility
+
 ### v0.6.4 (Ghidra versions < 11.4)
 * Export namespace support
 * Fix indefinite hang on diffing
-  
+
 ### v0.6.3
 * Allow table sorting
 
@@ -143,13 +146,15 @@ Sometimes it's useful to be able to debug the extension together with Ghidra, he
 
 1. Clone and build Ghidra and let gradle create eclipse projects according to the DevGuide
 1. Import the projects into eclipse (make sure it has relevant plugins for extension development)
+1. Install PyDev (http://www.pydev.org/updates as eclipse repository)
 1. [Install GhidraDev](https://github.com/NationalSecurityAgency/ghidra/blob/master/GhidraBuild/EclipsePlugins/GhidraDev/GhidraDevPlugin/README.md#manual-installation-in-eclipse-online)
 1. Unpack the Ghidra build and link GhidraDev to it. Maybe have to set `GHIDRA_INSTALL_DIR` environment variable
 1. Run Ghidra from eclipse and install BinExport extension
 1. Create BinDiffHelper eclipse project with `gradle build eclipse`
-1. Import it into eclipse and use GhidraDev to link it to the Ghidra build
+1. Import it into eclipse and use GhidraDev to link it to the Ghidra build.
 1. Debug As->Ghidra
 
+There might be some classpath clashes between the classpath generated by `gradle build eclipse` and the classpath modifications done by GhidraDev. It can help do remove all .jars from the core Ghidra Installation from the Extension project and let GhidraDev re-add them. If eclipse debugging fails afterwards, closing and reopening the extension project in eclipse can help.
 When debugging Ghidra with the extension out of eclipse, the extension is loaded into Ghidra automatically (don't go through the usual extension install). However, the plugin has to be enabled in the Code Explorer.