At 08:06 AM 4/14/00 -0400, you wrote:
>
> Hi,
>
> I just installed beta 23 and give it a run. After setting a breakpoint in my
> program I started the debugger. I was waiting for the JDE screen pop on top
> of my java program but everything stopped working. I had to use the Task
> Manager to kill my java program and the java debugging process to regain
> control of JDE. The problem is probably related to this new screen popping
> functionnality.
>
A freezeup indicates that a Lisp error is occuring in one of the functions
that enable the JDEbug menus. Indeed, your *messages* buffers shows that a Lisp
error did occur and the error is that a JDE function (probably a menu enabler)
is trying to access a slot in the process object that is not bound. I thought
in the latest release I had put guards against accessing unbound slots in all
menu enablers. Perhaps I missed one. Unfortunately, I need a backtrace in order
to determine which enabler is erroring out. You should be able to get a
backtrace by including
(setq debug-on-error t)
at the head of your .emacs file.
BTW, I recommend that everyone have debug enabled and include backtrace buffers
when reporting problems. (The Submit Propblem Report command,
jde-submit-problem-report, includes the backtrace buffer automatically in your
.emacs file.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The easiest
way to ensure that your report is complete is to include the output of the
JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
