illustrate:
1 This tool is mentioned in "Perspective JAVA-Decompilation Patching and Reverse Engineering Technology", here is a brief introduction
The latest version of 2ODB (ie Omniscient Debugger) has been migrated to github
3 The highest JDK version supported by ODB is 1.6 . The jar package and class used to analyze the new version will report various exceptions. From an inner point of view, I still don’t want to introduce this tool.
Use of OmniscientDebugger ODB
download
github way
https://github.com/OmniscientDebugger/LewisOmniscientDebugger/releases
maven central warehouse method
Instructions
1bat batch mode
Create a new Debugger directory in the root directory of the C drive
Copy LewisOmniscientDebugger-1.6.jar to this directory and rename it to debugger.jar
Open debugger.jar with winrar or extract it
Copy the debug.bat file in the Microsoft directory to the Debugger directory
Unzip the jar to be debugged to this directory such as ZKM
cd C:\Debugger
debug com.zelix.ZKM
This cannot be started under JDK1.8, and the stack frame exception is reported
2java -jar operation
use command
java -jar LewisOmniscientDebugger-1.5.jar
At this time, the class file selection window will pop up (there is file type filtering, only files with the suffix of class can be selected), select the main class file to analyze
Since I installed JDK1.8 locally, I don't want to make 1.6 for this tool. Click Demo to see the basic interface.
Where there are left and right arrows, you can click to see the changes in the stack and local variables