Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DRAFT, February 18, 2003, Page 78<br />
down), a toolbar or menu item to be accidentally selected, and similar strange effects. This is fixed in JDK<br />
1.3 final.<br />
Freeze up - jGRASP may freeze up when starting. If you kill it and start again, it is likely to run (possibly<br />
after several tries). Note that after killing jGRASP you will get a warning that there is a currently running<br />
instance; choose "Run Anyway" to continue.<br />
Memory leaks - due to Swing bugs, there are some small memory leaks. These have been minimized as<br />
much as was possible. Opening and closing a CSD window on the virtual desktop will leak up to 1K or so<br />
under some JDKs, so this should not be a problem unless you run jGRASP for weeks without restarting<br />
(like I do). There may be larger memory leaks that we are unaware of.<br />
Caps lock - the caps lock key will not work on some systems. Having caps lock on may also cause menu<br />
accelerators not to work.<br />
Display mode - jGRASP may not run with all display modes (color depths) on all systems. It probably<br />
won't run on Blackdown Linux with a 24-bit display (this is a problem with all Java apps) - haven't tried or<br />
investigated the latest Blackdown version yet.<br />
Bad dialog positions - due to Swing bugs, on some systems dialogs may pop up in strange positions,<br />
possibly off-screen. Clicking the menu item that brought up the dialog again will usually move it onscreen.<br />
GNOME - If you are using GNOME (the default desktop environment on RedHat 6), you may not be able<br />
to run jGRASP with some JDKs because of freeze-up (this is a problem with all Java apps).<br />
olvwm - on older versions of olvwm and possibly other window managers, the title bars may not show the<br />
title bar text (this is a problem with all Java apps). Install the latest olvwm to fix this (or bug your sysadmin<br />
into installing it).<br />
Solaris JDK 1.2 problems (you should not use 1.2):<br />
Dialog layout is often messed up, with buttons off-screen or extra empty space.<br />
Find and replace does not see the find text most of the time. Sometimes hitting "Enter" will make<br />
it work. If you highlight the search text then pop up the dialog, that will work. Since the replace<br />
text may not be recognized, "Replace All" is very dangerous.<br />
14 Future Features / Missing Features<br />
Check the future plans page at http://www.eng.auburn.edu/grasp/ for an updated list of planned future<br />
features, if you are not already there.<br />
Short Term / Ongoing<br />
Navigation (for Java first).<br />
More features for the integrated Java debugger: show new and changed values in a different<br />
color; hex and octal display for values and array indeces; a dynamically updated monitor display<br />
window, listing owning thread and waiting threads by monitor; automatic deadlock detection; byte<br />
code display; display of current watchpoints to make removing them easier; ability to set<br />
breakpoints without access to source code; repeated, animation-like stepping; counted stepping<br />
(eg: step in 42 steps); ability to change values while debugging; ability to disable/enable garbage<br />
collection for objects; assistance for memory leak (lost reference) detection; exception<br />
breakpoints; listing of all loaded classes with their fields and methods; show classpath, version,<br />
and other information for target VM; tracing variable changes; dumping of thread, stack, and<br />
variables to message window for easy cut-and-paste.<br />
A debugger connection and interface for languages other than Java.
Change language