JDebugTool Graphical Java Debugger
--------------------------------------------------------------------------------
debugtools.com™ LLC is the maker of the JDebugTool® graphical Java™ debugger:
A standalone Java debugger.
Built on top of the standard JPDA (Java Platform Debugger Architecture).
Is itself written in Java.
Features an intuitive and graphical Java Swing GUI.
Context sensitive Help Viewer.
JDebugTool is featured in Sun's Swing Sightings 11.
News: JDebugTool 4.0.3 -- November 25, 2007
--------------------------------------------------------------------------------
Programmers spend a lot of time debugging:
On some projects, debugging occupies as much as 50 percent of the total development time. For many programmers, debugging is the hardest part of programming.1
You need good debugging tools:
Debugging tools are powerful aids to software development. Find them and use them.1
Code Complete by Steve McConnell
--------------------------------------------------------------------------------
Track down bugs faster with JDebugTool:
Line and method breakpoints.
Breakpoint Groups.
Local and Remote debugging.
Run, Attach and Listen.
User friendly GUI.
Multi-Thread debugging.
Display and traverse stack backtraces.
Data Tool Tips.
Hot Swap classes and Pop stack frames.
Save settings in Projects.
Display variables in current scope.
Drill down into object references.
Modify primitive variables.
Display loaded classes.
Display toString() results.
Display Chained Exceptions.
Evaluate simple Expressions including Method Calls.
Stop on Thread Start and Death events.
Stop on Class Load and Unload events.
Stop on Method Entry and Exit events.
Stop on Field Watchpoint events.
Navigate source code structure.
Launch External Text Editor.
More features
--------------------------------------------------------------------------------
Two important principles of debugging:
If you don't see the bug where you're looking, perhaps you're looking in the wrong place.1
The place where you find bugs may not be the right place to put a fix in.... I'd do some digging and find the root cause.2
James Gosling - the creator of Java
Brian Harry - "the Java bug fixer"
