What's new in JDebugTool 5.0.5
Sep 15, 2010
- This release works around some possible JFileChooser defects.
New in JDebugTool 4.5.5 (May 11, 2010)
- This release fixes some minor defects.
New in JDebugTool 4.5.4 (May 4, 2010)
- This release enhances the tool tips in the Breakpoints, Exceptions, Watchpoints, Threads, Stack, and Loaded Classes Panels.
- Clears the previous results in the String/To String Window on the start of a new debug session, rather than when the previous debug session terminated.
New in JDebugTool 4.5.3 (Apr 26, 2010)
- This release improves the top-level Objects Window, from a tabbed style window, into a tree/table style window
New in JDebugTool 4.5.1 (Apr 19, 2010)
- This release improves the String/To String top-level window, from a tabbed style window, into a list selection style window.
- Improves the Events top-level window, from a tabbed style window, into a list selection style window.
New in JDebugTool 4.5 (Apr 19, 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.7 (Apr 6, 2010)
- This release now refreshes the Threads Panel, in the background when the target JVM is suspended.
New in JDebugTool 4.4.6 (Apr 6, 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 26, 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 17, 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 11, 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 (Feb 16, 2010)
- In this release, the Loaded Classes panel now displays ClassLoader information.
New in JDebugTool 4.3.3 (Feb 9, 2010)
- This release improves the Loaded Classes panel:
- 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.1 (Nov 28, 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.3 (Nov 28, 2009)
- In this release, if the result of an expression in the Expressions Panel is an object reference, then the current values of the object's fields will be displayed.
- If the result of an expression in the Expressions Panel is an array reference, then the current values of the beginning array elements will be displayed.
- If the result of an expression in the Expressions Panel is a string reference, then the beginning contents of the string will be displayed.
- In the Global Settings (Edit | Global Settings...) there is now a new setting: Hint for the max. number of lines in an Expression result. This is a hint for the maximum number of lines of an expression result to display in the Expressions Panel in the GUI. For example, the number of fields in an object, or the number of array elements, to display. Defaults to 20.
New in JDebugTool 4.2.3 (Nov 28, 2009)
- In this release, 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, including (new in this release) superclasses in the inheritance hierarchy.
New in JDebugTool 4.2.2 (Nov 28, 2009)
- In this release, in the Global Settings (Edit | Global Settings...) there is now a new setting: Hint for the max. number of lines in a Tool Tip. This is a hint for the maximum number of lines to display in a pop-up Tool Tip in the GUI. For example, the number of fields in an object, or the number of array elements, to display in a Tool Tip. Defaults to 20.
- The current execution point indicator in the source code display, is now cleared immediately when the target JVM starts executing, for example with a Step or Resume All operation.
New in JDebugTool 4.2.1 (Nov 28, 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.0 (Apr 3, 2009)
- In this release, hovering the mouse over an object reference in the source code, 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 source code, 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 source code, will display a multi-line tool tip showing the beginning contents of the string.
New in JDebugTool 4.1.4 (Jan 15, 2009)
- In this release, JDebugTool will now start up even if the tools.jar file is not in the classpath 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 classpath 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 30, 2008)
- In this release, the tool tips 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(s) 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.
New in JDebugTool 4.1.1 (Jul 11, 2008)
- In this release, the locations of the main panel splitters (sliders) in the GUI are now remembered persistently between JDebugTool invocations.
- In the String/To String top-level Frame, duplicate strings will no longer be displayed twice. If a string is already being displayed, then the corresponding tab will be brought to the top.
New in JDebugTool 4.1 (May 21, 2008)
- In this release, the Objects, String/To String and Events windows are now top-level Frames, instead of dialogs.
- The screen locations and sizes of the top-level Frames in the GUI are now remembered persistently between JDebugTool invocations.
New in JDebugTool 3.11.2 Pro (Jul 5, 2007)
- This release adds a 48x48 desktop icon to the jdebugtool.ico icon file (Help | Desktop Icon...).
- JDebugTool will no longer try to automatically copy the tools.jar file, but will instead provide the instructions for the user to manually copy the tools.jar file
- The Target | Memory... and Target | Properties... menu items are no longer supported.