SlickEdit Community

Archived Beta Discussions => SlickEdit 201x Beta Discussions => SlickEdit 2014 v19 beta => Topic started by: Marcel on October 13, 2014, 02:34:33 PM

Title: B6: Trace option for Java debugger (W7-x74)
Post by: Marcel on October 13, 2014, 02:34:33 PM

Is there any way to turn on some tracing around the interactions between the Java debugger included with SE and the VM?
I am fighting recurring hangs while trying to debug (larger) J8 application. For example, stepping over a line of code just hangs (no CPU activity). Hitting 'suspend' at that point gives me UI control back but now the interactions with the debugger appear to be out of step, i.e. it feels like a delicately balanced request-response scheme got out of sync and the debugger is processing VM responses one-off.

Title: Re: B6: Trace option for Java debugger (W7-x74)
Post by: Dennis on October 13, 2014, 04:01:46 PM

Macro > Set Macro Variable > def_debug_logging = 1

Look at the results in <config>/logs/debug.log

Remember to turn it off when you are done, it does a LOT of logging, and creates a bit of overhead.  The output is kind of messy, but can be deciphered.

Title: Re: B6: Trace option for Java debugger (W7-x74)
Post by: Marcel on October 13, 2014, 05:14:27 PM

Thanks Dennis.
I captured a debug session.  There is a long break in the log while I was waiting for the debugger to hit the next breakpoint. It didn't until I suspended the session. 

debug[2014-10-13T10:46:09.632000Z]JDWP reply:    error_code=0
debug[2014-10-13T10:52:11.491000Z]JDWP send:    command_set=VirtualMachine(1)