If you debug an app compiled with debugging enabled, --but that app in turns uses a jar file that has no debug information, you hit the following:
once you turn on local variables display, jde sends out the command for retrieving locals, gets a null and displays a lisp error in *Messages*. However the rest of jde then appears to think the debugger didn't respond. Here are the corresponding lines from *JDEBug* and *Messages* (jde-dbo-command-result 16 (list (cons (list "parser" "org.apache.xerces.dom3.as.DOMASBuilder") (list "org.apache.xerces.parsers.DOMASBuilderImpl" 416 nil)) (cons (list "domImpl" "org.apache.xerces.dom3.as.DOMImplementationAS") (list "org.apache.xerces.dom.DOMImplementationImpl" 223 nil)) (cons (list "argv" "java.lang.String[]") (list "java.lang.String[]" 217 nil)))) JDE> 1 17 get_this 1 0 (jde-dbo-command-result 17 (list "null")) *Messages*: (or object-p class-p) nil) Running dom.ASBuilder. -- Best Regards, --raman ------------------------------------------------------------ T. V. Raman: PhD (Cornell University) IBM Research: Human Language Technologies Architect: Conversational And Multimodal WWW Standards Phone: 1 (408) 927 2608 Fax: 1 (408) 927 3012 Email: [EMAIL PROTECTED] WWW: http://www.cs.cornell.edu/home/raman AIM: TVRaman PGP: http://emacspeak.sf.net/raman.asc Snail: IBM Almaden Research Center, 650 Harry Road San Jose 95120
