JDEbug

[Mark Dopheide]

 

This is a summary of my recent experience (and problems) running JDEBug v. 2.3.1, hopefully these comments will be useful to others. Certainly any comments from others with similar (or contradictory) experience would be helpful to me. I'm running Windows2000 w/ cygwin, xemacs 21.4.10, jdk1.3 and weblogic6.1

 

Overall, I find it prudent to start a new xemacs session solely for debugging purposes since I find I need to exit xemacs at the end of each debugging session to get it to re-initialize and start a new debug session properly.

 

I wasn't able to attach (or listen to) a servlet process using shared memory. Using sockets to "attach" works for me, but sockets didn't work for "listen" (Java Debug Ref. Implementation v 1.3:

When attached successfully I see:

        Attached to process on port 1959 of local host.
        Setting breakpoint at line 671 in                       

        c:/dev/wml/src/common/com/wml/arch/admin/MemberRepository.java.
        Attached VM (socket) Java Debug Interface (Reference Implementation) version 1.3
        Java Debug Wire Protocol (Reference Implementation) version 1.0
        JVM Debug Interface version 1.0
        JVM version 1.3.1 (Classic VM, native threads, nojit)

Toggling breakpoints off doesn't seem to work. I am able to toggle breakpoints on and off before I start the debugger. But when I try to toggle them off after I start the debugger then I get "Symbol's value as variable is void: old-assoc". Once the breakpoint is set, execution will stop at the breakpoint however. I have also seen the message "Wrong type argument: extent-live-p, #<destroyed extent>

 

JDEbug->processes->detach process: doesn't seem to work and the familiar message appears ("Symbol's value as variable is void: old-assoc")

 

JDEbug->Exit Debugger doesn't seem to work ("Symbol's value as variable is void: old-assoc"), although killing the *JDEbug* buffer does seem to stop it

 

I find some of the documentation is slightly out of date (broken links to JDB, JPDA info missing/obsolete)

 

This product is going in a fantastic direction, I congratulate everyone involved and eagerly await new versions.

 

Mark