JDebugTool Changelog

What's new in JDebugTool 5.0.5

Sep 6, 2010
  • This release works around some possible JFileChooser defects.

New in JDebugTool 5.0.3 (Jun 15, 2010)

  • This release fixes a defect where sorting by clicking on a table column header in a table displaying Java variables, would cause the row based tool tips to become out of sync.

New in JDebugTool 5.0.2 (Jun 8, 2010)

  • This release now saves watchpoints (that are not constrained to a particular object instance) in the project settings.

New in JDebugTool 5.0.1 (Jun 2, 2010)

  • This release colorizes the output from the Expressions panel.
  • The CLASSPATH dialog (displayed from the Run dialog), now has separate buttons for Add Directory and for Add Jar File.

New in JDebugTool 4.5 (Apr 12, 2010)

  • This release adds an option for a six resizable division layout (in addition to the current four resizable division layout) for the JDebugTool main window. Defaults to six, if your screen is wide enough. Select Global Settings... from the Edit menu.

New in JDebugTool 4.4.6 (Mar 30, 2010)

  • This release adds a Display Initial Classes on Connection project setting (defaults to false). JDebugTool can query for all the classes already loaded in the target JVM, when JDebugTool initially connects to the target. Right-click in the Loaded Classes panel and select Display Initial Classes...
  • Now refreshes the Objects Frame, in the background when the target is suspended.

New in JDebugTool 4.4.5 (Mar 24, 2010)

  • This release now computes the initial set of classes displayed in the Loaded Classes panel, in the background.
  • Improves the responsiveness of the GUI, upon the initial connection with the target JVM.

New in JDebugTool 4.4.4 (Mar 16, 2010)

  • This release now displays classes in the Loaded Classes panel, as they are loaded in the target JVM.
  • Improves single stepping performance.

New in JDebugTool 4.4.3 (Mar 10, 2010)

  • This release supports breakpoints, exceptions, and watchpoints when the same class is loaded multiple times (by multiple ClassLoaders) in the target JVM.
  • The Resolved column (and corresponding tool tips) in the Breakpoints, Exceptions, and Watchpoints panels (select Columns...from the right-click pop-up menu) is now ClassLoader aware.

New in JDebugTool 4.4.2 (Feb 26, 2010)

  • This release improves the validation of input typed into JDebugTool dialogs, and project settings.
  • Improves tool tip display of long class names (including package names).
  • Improves tool tip display of long file paths.

New in JDebugTool 4.4.1 (Feb 19, 2010)

  • In this release, to create a breakpoint when a particular method is called, navigate to the method body in the source code. Click to place the blinking cursor anywhere on the same line as the method name in the method signature, and then select Set Method Breakpoint from the right-click pop-up menu.
  • Fixes defect where invalid breakpoints could get displayed in the line number column in certain cases.
  • Fixes defect where shared memory listen would not release the shared memory.

New in JDebugTool 4.4 (Feb 12, 2010)

  • In this release, the Loaded Classes panel now displays ClassLoader information.

New in JDebugTool 4.3.3 (Feb 5, 2010)

  • Now only displays classes that are at least in the target JVM "prepared" state.
  • No longer displays array classes.
  • No longer displays package names in type names for method arguments and return value, local variables, fields, and superclass names.

New in JDebugTool 4.3.2 (Jan 29, 2010)

  • In this release, incorrectly mounted source paths can now be automatically detected and fixed by JDebugTool. In the Source Tree panel, under an incorrectly mounted source path, click on a Java source file in order to display the file. JDebugTool will then automatically unmount the incorrect source path, and then automatically mount the corresponding correct source path, after prompting the user.

New in JDebugTool 4.3.1 (Nov 25, 2009)

  • In this release, to drill down into an object reference, simply click on an object reference (including array and string references) in the source code display, and then click on the Inspect... button in the tool bar (or right-click and select Inspect...).
  • To invoke the toString() method on an object reference, simply click on an object reference in the source code display, and right-click and select toString...
  • To watch a variable, simply click on a variable in the source code display, and right-click and select Add to Watch Panel 1 or Add to Watch Panel 2.
  • For all the above operations, it is no longer necessary to first highlight the entire variable or object reference in the source code. Simply clicking on the variable or object reference in the source code is sufficient. Use the source code tool tips as hints to which variable or object reference is active in the source code display.
  • Hovering the mouse over an object reference in the GUI, will display a multi-line tool tip showing the current value of the object's fields in the inheritance hierarchy, including (new in this release) displaying implemented interfaces names.

New in JDebugTool 4.2.1 (May 26, 2009)

  • In this release, hovering the mouse over an object reference in the Locals, This, Watch or Objects windows, will display a multi-line tool tip showing the current values of the object's fields.
  • Hovering the mouse over an array reference in the Locals, This, Watch or Objects windows, will display a multi-line tool tip showing the current values of the beginning array elements.
  • Hovering the mouse over a string reference in the Locals, This, Watch or Objects windows, will display a multi-line tool tip showing the beginning contents of the string.

New in JDebugTool 4.2 (Mar 22, 2009)

  • In this release, hovering the mouse over an object reference in the source code will display a multi-line tooltip showing the current values of the object's fields.
  • Hovering the mouse over an array reference in the source code will display a multi-line tooltip showing the current values of the beginning array elements.
  • Hovering the mouse over a string reference in the source code will display a multi-line tooltip showing the beginning contents of the string.

New in JDebugTool 4.1.4 (Dec 28, 2008)

  • This release will now start up even if the tools.jar file is not in the class path used to invoke JDebugTool.
  • The parts of the GUI that do not depend upon tools.jar are still usable.
  • However, in order to actually debug a target JVM, the tools.jar must be present in the class path used to invoke JDebugTool.
  • The Stepping Excludes (Execution | Excludes...) no longer mask explicitly opening a Java source file (for example, clicking on a Java source file in the Source Tree panel).

New in JDebugTool 4.1.3 (Oct 26, 2008)

  • In this release, the tooltips on the tabs in the Objects and String/To String top-level Frames, now display the object paths taken to "drill down" to the object displayed in that tab.
  • Hot Swap will now remember the root directory/directories of the class files that are hot-swapped, so that subsequent hot-swap operations on class files in the same class file hierarchies will no longer require the user to navigate in the File Chooser dialog each time to the class file.
  • The File Chooser dialog will now open to the anticipated class file to hot-swap automatically.