Robert Mecklenburg writes: > I've just tried using the jdb support in jdee again (I'd tried about a > year ago and gave up). It seems to be working fairly well for me. > Thank you! I do have some problems which I'll summarize here. If you > want more complete bug reports I'm happy to send them. I just don't > want to clutter the list if these are known or have already been fixed > or aren't bugs at all. This list is gathered after about 15 debugging > sessions over three days. > > 1. If the *debug window is ever hidden, I must cause it to reappear > by hand (C-x 2, C-x b ...). It would be nice if normal > jde-debug-* commands ensured the *debug window was visible. >
The JDEE tries to ensure this. Can you please describe the circumstances in which it fails for you. > 2. The user doc said I can run jdb with M-x jde-jdb. When I do I > get: > > apply: Wrong number of arguments: #[(this main-class) "A++" > ["Launch the application whose main class is MAIN-CLASS in debug > mode."] 1 "Launch the application whose main class is MAIN-CLASS > in debug mode."], 1 > > Using jde-debug (which isn't in the doc) works fine. > jde-jdb is obsolete. I've fixed the doc to reflect this. > 3. After setting a breakpoint and debugging. More often than not, I > cannot remove the highlighting from a breakpoint line. That is, > after the program exits (or I quit) the highlighting remains and > toggling the breakpoint on that line does not clear the > highlighting. > I too have seen this occasionally but I can't remember the circumstances and can't reproduce it. Can you describe the cases in which this occurs. > 4. It seems to me that when I invoked jde-debug on a java file which > didn't have a .class file, the jde would start up a javaw.exe > which remained running even after jdb quit and which hosed the > jde. That is, subsequent invocations of jde-debug yeilded jdbs > that generated errors and could not be used for debugging. This, > of course, happens by accident fairly regularly. > Again I cannot reproduce this. I tried deleting all the class files for my test case and runnding jdb. jdb simply gave a "class not found error." I was then able to exit jdb, recompile my test app, and run jdb again without any problems. Can you be more specific about the case(s) where this happens? > 5. Quite often (always?), when I quit jdb in the middle of executing > a program, the jdb would appear to exit and leave the debugee to > continue executing. For the application I'm working on this is > quite a hassle since it goes on to corrupt data files which then > need to restored from copies. It would certainly be nice (for me) > if quitting jdb terminated the application. > If jdb starts the program, it should kill the program. I've never encountered a case where it does not do this. If it is not killing the debuggee program in your case, you should report this to Sun. > 6. This is not really a "Problem", but is more of a "problem" (small > issue). When the jde-debug command executes it switches buffers > to the jdb window. I like this and would prefer to do my > debugging in the jdb window. I've added gud-mode-like keybindings > for this mode with a hook, but when I invoke, say > jde-debug-step-into, the jdb window is replaced by the source code > window. I would like to debug from the jdb window because in that > mode I can rebind function keys and control keys appropriately for > debugging - keys which already have binding under jde-mode in the > source window. What I would like is a split-window arrangement > (source and jdb) where jde-debug-step-into does not switch buffers > or replace the jdb window. > I am planning to enhance the jdb interface so that you can do gud-like stepping from the source buffer, i.e., single key strokes, such as "s" for step in, "n" for step over, etc. The JDEE already tries to maintain a gud-like split-screen user interface. If it is failing in your case, I need a detailed description of the circumstances so I can reproduce it. - Paul
