Neeraj Apte writes: > Hi Paul, > thanks for your prompt response. I am not sure I have tried JDEE's new > interface. I have been able to attach to weblogic (the external process) > via a socket/shared memory. Is that what you are referring to? > The problem is that once I attach, it starts printing these messages and bogs > down weblogic so much that I cannot reach the point that I want to > debug. I understand that turning the debug messages off will help. However, is > there something fundamentally different between jdb and other debuggers > like JSwat? While jdb/weblogic gets bogged down and sometimes completely hangs, > JSwat/Weblogic seems to work very smoothly and lot faster for the same > application.
Hi Neeraj, The JDEE supports TWO debuggers: - jdb, which is the command-line debugger shipped with the JDK and for which the JDEE provides an Emacs interface that turns it into a source level debugger. - JDEbug, which is a debugger developed originally by a Sun Microsystems summer intern for use with the JDEE In theory, JDEbug is more powerful than jdb but unfortunately it needs a LOT of work to improve both performance and stability before it can be considered really useful. On the other hand, jdb is fairly stable and so is the JDEE interface to jdb. My expectation is that JDEE users will use the JDEE's jdb interface for routine debugging until JDEbug stabilizes or perhaps is replaced with a JDEE interface to JSWAT as some have suggested. I and others put a fair amount of work into stabilizing and enhancing the JDEE's interface to jdb for JDEE 2.3.3. I've been using jdb to debug the project that I'm currently working on here at The MathWorks and I'm pretty happy with the result. I'm interested in getting feedback from others on this work. So I'd appreciate it, if you would take a stab at using the jdb interface. Use M-x customize-variable jde-debugger to select the jdb interface and then select Help from the Jdb menu to display the Jdb User's Guide. - Paul
