Hi. I'm an experienced XEmacs user but new to JDEE, and I'm having
trouble getting JDEbug to work properly. I think I'm close, but a
number of odd things are happening.
Since my company's XEmacs was only v20.4, I downloaded the most recent
version from xemacs.org, including the sumo tarball. The JDEE in the
tarball gave me trouble so I instead downloaded the latest version from
jde.sunsite.dk. I read the user's guide and set up my .emacs file
accordingly, customizing the following variables:
(setq defer-loading-jde t)
...
(custom-set-variables
'(jde-compile-option-debug (quote ("all" (t nil nil))))
'(jde-db-debugger (quote ("JDEbug" "" . "Executable")))
'(jde-bug-jpda-directory (expand-file-name "~/local"))
'(jde-bug-debugger-command-timeout 3)
'(jde-db-source-directories (list (getenv "SRC") (expand-file-name
"~/src/test"))))
I'm running JDK 1.2.2_06 on Solaris 8 (hence the jde-bug-jpda-directory
override).
For my load-path, I overrode only the JDEE location since the sumo
tarball contains what appear to be the most recent versions of EIEIO,
semantic, and speedbar. Here are the versions I'm using:
- emacs-version "21.1 (patch 9) \"Canyonlands\" XEmacs Lucid"
- eieio-version "0.16"
- speedbar-version "0.13"
- semantic-version "1.4beta8"
- jde-version "2.2.8"
My test app is a simple text-based program that constructs a couple of
classes and dumps out their contents. It works great from my bash
shell.
Upon invoking XEmacs and loading my source file, JDE loads fine, runs my
(do-nothing) jde-mode-hook, and correctly updates the menu bar to
include JDE and JDEbug. I select JDEbug->Processes->StartDebugger,
which causes "Debugger started successfully" to appear. So far, so
good.
Problem #1: the first time I select JDEbug->Processes->LaunchProcess, I
get "No response to command 1. (process = 1; timeout = 3 sec)". The
second time I launch my app, the XEmacs window splits in three the way
I'd expect and enters the debugger. Well, usually it does. Sometimes I
have to launch the app several times before it comes up. Sometimes it
never comes up.
Problem #2: When JDEbug does manage to launch my app, I set a couple of
breakpoints and select JDEbug->Continue. The => indicator shows up at
the correct source line and I can step through the source using
JDEbug->StepOver. But the => indicator seems to jump over too may
source lines and gets out of sync with the CLI buffer. Eventually I get
all the way through the program but the indicator never gets back in
sync.
Problem #3: Sometimes nothing appears in my CLI buffer. Other times it
contains "CLI exited abnormally with code 256" but nothing else. I'm
not sure whether the program is hung or its output just went to the bit
bucket.
Problem #4: Sometimes the debugger runs the app OK but just blasts on
through, ignoring any breakpoints I've set. All output appears the way
I'd expect, but this isn't very useful for debugging. ;-)
Since I've seen quite a few raves about JDEE and JDEbug I'm sure my
troubles are due to pilot error, either in my selection of packages or
my setup. If anyone would like to help me out with this I'd be glad to
send along a copy of my .emacs file and any other information that will
help. I'd really appreciate some guidance since if I can't get JDEE to
work I'll probably be stuck using (ugh!) Forte.
Thanks.
Elliott
