RE: Using JDEbug to debug a J2EE app
Paul Ah, I might try that. I'm not criticising the key sequences, that's how emacs is. What I'm saying is that, as a command-line junky, its nice to be able to sit there with my fingers on the home keys typing next, next, step, print foo, etc. Regards David > -Original Message- > From: Paul Kinnucan [mailto:[EMAIL PROTECTED] > Sent: 11 July 2003 13:34 > To: Lord, David - CSG > Cc: [EMAIL PROTECTED] > Subject: RE: Using JDEbug to debug a J2EE app > > > Lord, David - CSG writes: > > Hi Paul > > > > I've been using jdb on JBoss (I tried JDEbug but it was > too slow) and it > > works great. The only niggle I would have is with > useability. I find it > > easier to type commands at the console than using the > rather convoluted > > control key sequences, but every time the source file > changes it loads in > > the same window as the console, thus hiding it. > > > > Have you tried customizing the keys via jde-jdb-key-bindings. The > "convoluted" control sequences are forced as defaults upon > the JDEE by Emacs conventions intended to prevent conflicts > among Emacs packages. That doesn't mean that individual > users can'd define keys anyway they like. For example, I > assign function keys to the most common Jdb commands. In the > future, I plan to provide single-letter key bindings for > the commands. > > - Paul > ** This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use any part of it - please delete all copies immediately and notify the Hays Group Email Helpdesk at [EMAIL PROTECTED] Any information, statements or opinions contained in this message (including any attachments) are given by the author. They are not given on behalf of Hays unless subsequently confirmed by an individual other than the author who is duly authorised to represent Hays. A member of the Hays plc group of companies. Hays plc is registered in England and Wales number 2150950. Registered Office Hays House Millmead Guildford Surrey GU2 4HJ. **
RE: Using JDEbug to debug a J2EE app
Lord, David - CSG writes: > Hi Paul > > I've been using jdb on JBoss (I tried JDEbug but it was too slow) and it > works great. The only niggle I would have is with useability. I find it > easier to type commands at the console than using the rather convoluted > control key sequences, but every time the source file changes it loads in > the same window as the console, thus hiding it. > Have you tried customizing the keys via jde-jdb-key-bindings. The "convoluted" control sequences are forced as defaults upon the JDEE by Emacs conventions intended to prevent conflicts among Emacs packages. That doesn't mean that individual users can'd define keys anyway they like. For example, I assign function keys to the most common Jdb commands. In the future, I plan to provide single-letter key bindings for the commands. - Paul
RE: Using JDEbug to debug a J2EE app
Hi Paul I've been using jdb on JBoss (I tried JDEbug but it was too slow) and it works great. The only niggle I would have is with useability. I find it easier to type commands at the console than using the rather convoluted control key sequences, but every time the source file changes it loads in the same window as the console, thus hiding it. Regards David > -Original Message- > From: Paul Kinnucan [mailto:[EMAIL PROTECTED] > Sent: 10 July 2003 18:55 > To: Neeraj Apte > Cc: 'Paul Kinnucan'; [EMAIL PROTECTED] > Subject: RE: Using JDEbug to debug a J2EE app > > > 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 > ** This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use any part of it - please delete all copies immediately and notify the Hays Group Email Helpdesk at [EMAIL PROTECTED] Any information, statements or opinions contained in this message (including any attachments) are given by the author. They are not given on behalf of Hays unless subsequently confirmed by an individual other than the author who is duly authorised to represent Hays. A member of the Hays plc group of companies. Hays plc is registered in England and Wales number 2150950. Registered Office Hays House Millmead Guildford Surrey GU2 4HJ. **
RE: Using JDEbug to debug a J2EE app
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
RE: Using JDEbug to debug a J2EE app
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.
Thanks,
- Neeraj
-Original Message-
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2003 10:21 AM
To: Neeraj Apte
Cc: 'Paul Kinnucan'; [EMAIL PROTECTED]
Subject: Using JDEbug to debug a J2EE app
Neeraj Apte writes:
> Hi,
>I have been trying to use the debugger from the latest beta(5) of JDEE to debug
> an enterprise application running within weblogic, but it keeps
> printing the following messages (I think for every method call or something):
Hi Neeraj,
Those are messages for debugging the debugger. I'll turn them off in the next release.
Have you tried the JDEE's new interface to jdb? You should be able to use it to debug
a weblogic app as it allows attaching to an external process.
- Paul
> -8<---8<
> Debug message: 3:58:20 PM: EventHandler: sending event
> jde.debugger.EventSetEvent[eventSet=event set, policy:2, count:1 =
> {ClassPrepareEvent in
thread
> ExecuteThread: '12' for queue: 'default'},suspended=false,threadRef=instance of
> weblogic.kernel.ExecuteThread(name='ExecuteThread: '12' for queue:
> 'default'', id=2)]
> Debug message: 3:58:20 PM: EventHandler: sending resume event to [EMAIL PROTECTED]
> Debug message: 3:58:22 PM: EventHandler: VM resumed
> Debug message: 3:58:22 PM: EventHandler: sending resume event to [EMAIL PROTECTED]
> Debug message: 3:58:22 PM: EventHandler: VM resumed
> Debug message: 3:58:22 PM: JDEbug got cmd
> Debug message: 3:58:22 PM: JDEbug firing command event
> Debug message: 3:58:22 PM: proc: 1 got command:
> jde.debugger.CommandEvent[m_procId=1,m_cmdId=3,m_cmdName=finish,m_args=[]]
> Debug message: 3:58:22 PM: JDEbug command is jde.debugger.command.Finish
> Debug message: 3:58:22 PM: JDEbug waiting for cmd
> -8<---8<
>
> As a result, it's too darn slow and it makes the debugger virtually useless.
>
> Am I doing something wrong in terms of set up?
> Any help would be greatly appreciated.
> Thanks,
>
> - Neeraj
