Community
Participate
Working Groups
code from HEAD Steps: 1. set a breakpoint in a script that is loaded in the Rhino VM 2. connect the debugger to the VM 3. trace the socket communication Expected: when the target connects I would expect to see a setbreakpoint request sent for the existing breakpoint, and the VMs' response Happens: we do send out the request, and we do get the VMs' response, but immediately following we send out a clearbreakpoint request for the bp we just requested to be set. We then get the VMs' response confirming the bp is cleared, and we then send another setbreakpoint request for the same bp we just set/removed. Not only is this 2x the work, but we are also artificially inflating the breakpoint ids
Created attachment 180282 [details] proposed fix I found that is the breakpoint is touched in any way we hit a call-back in our debug target the kills + recreates the bp. The patch removes this behavior.
applied patch to HEAD