Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352928

Summary: Debugging in reverse (reverse engineering)
Product: [Eclipse Project] JDT Reporter: Jonathan Camilleri <camilleri.jon>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3    
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Jonathan Camilleri CLA 2011-07-23 07:02:38 EDT 
Build Identifier:  M20110210-1200

It would be nice if when debugging code, it was possible to include the calling method by way of having a reverse function of the step functions (e.g. step through, step into, step out, run code), that provides for reverse engineering of code.

This is particularly useful to security analysts, and, support developers who are studying code which might be legacy code that was developed in a non readable manner, or perhaps by a malicious coder of a virus/worm/malware who intentionally obfuscates readability of code.

Donations are accepted if you think that this idea would be helpful :)

Reproducible: Sometimes
Comment 1 Jonathan Camilleri CLA 2011-07-24 01:37:42 EDT 
The following research paper might be useful to providing insights into designing a design navigator: http://essex.academia.edu/JonNicholson/Papers/587502/The_Design_Navigator_Charting_Java_Programs.