Author Topic: RC5, MacOS X, Unimplemented command error debugging perl project  (Read 2697 times)

tuchman

  • Senior Community Member
  • Posts: 144
  • Hero Points: 7
RC5, MacOS X, Unimplemented command error debugging perl project
« on: November 18, 2014, 06:05:38 AM »
Each time I "project_debug" into a perl project with breakpoint set that should be hit, SE goes unresponsive for ~5 seconds, then I see an error message shortly in the "autos" window, "values" column (not there long enough for me to read). 
Then debugging session ends. 
Attached is a debug log that contains:
<response xmlns="urn:debugger_protocol_v1" command="context_get"
               transaction_id="31" ><error code="4" apperr="4">
               <message>command 'context_get' not currently supported</message>
               </error></response>
debug[2014-11-18T06:55:22.205449Z]DBGp command_reply: command=context_get
debug[2014-11-18T06:55:22.220548Z]>>>>DBGP EVENT: type=response
  reason=ok
  status=stopping
  transaction_id=24
  command=run

Rodney

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 798
  • Hero Points: 54
Re: RC5, MacOS X, Unimplemented command error debugging perl project
« Reply #1 on: November 19, 2014, 09:50:54 PM »
context_get is disabled when the script stops executing, so this is normal.

Edit: Have you set up any mappings? It doesn't look like it, but I like to be sure.

Try exiting, deleting the .vpwhistu file and trying again. You'll have to set breakpoints again. Keep it simple.

Try a clean config.

If none of that is elucidating, then please send me an example project that reproduces the problem along with steps to reproduce (e.g. where to set the breakpoint etc.). Thanks.

++rodney
« Last Edit: November 19, 2014, 09:53:11 PM by Rodney »

tuchman

  • Senior Community Member
  • Posts: 144
  • Hero Points: 7
Re: RC5, MacOS X, Unimplemented command error debugging perl project
« Reply #2 on: November 20, 2014, 06:10:57 AM »
Hmmmm... 
I didn't change a line of code, same breakpoint, no changes to SE, and the problem can no longer be reproduced.
I did reboot the Mac in between debug sessions.