Changes between Version 3 and Version 4 of JavascriptDebugging


Ignore:
Timestamp:
Jan 14, 2013, 9:42:19 PM (11 years ago)
Author:
Yves
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JavascriptDebugging

    v3 v4  
    2323
    2424=== Toggling (setting/removing) breakpoints: ===
    25 Command:
    2625{{{
    2726http://127.0.0.1:9000/ToggleBreakpoint?filename=gui/gamesetup/gamesetup.js&line=1502
     
    5756Note: The command has no effect if the thread is not stopped.
    5857
     58=== Step ===
     59Step the execution. Honestly I'm not sure what it exactly does at the moment.
     60After calling it a few times it steps to the next line. Probably it executes each assignment/operation separately.
     61I will figure it out and improve for a next patch.
     62{{{
     63http://127.0.0.1:9000/Step?threadDebuggerID=1
     64}}}
     65
     66Arguments:
     67 * threadDebuggerID: The ThreadDebuggerID of the thread that should be stepped. You can get this ID by calling GetThreadDebuggerStatus.
     68
     69Returns:
     70Nothing
     71
     72
     73=== Getting Callstacks ===
     74Returns the callstacks of all threads that are in break mode.
     75{{{
     76http://127.0.0.1:9000/GetAllCallstacks
     77}}}
     78
     79Returns:
     80{{{
     81{ "CallStacks" : [{"ThreadDebuggerID" : 1, "CallStack" : ["keywordTestOR","annonymous","testFilter","initMapNameList","selectMapType","__eventhandler31 (selectionchange)","initMain","onTick","__eventhandler28 (tick)"]}] }
     82}}}
     83keywordTestOR is the innermost function which got called by an annonymous function, which got called by "testFilter" etc...
     84You also get the ThreadDebuggerID to know which thread is meant.
     85
     86
    5987
    6088{{{