Session using the restart command as usual.Īnother way to stop a debugging session is just interrupting redis-cli Redis-cli returns in its normal non-debugging mode. When the scripts terminates naturally, the debugging session ends and If you use continue in order to execute the script till the next breakpoint, commands will not be dumped on the screen to prevent too much output. Note that this happens only in stepping mode. The and lines show the command executed by the line justĮxecuted, and the reply from the server. While you step Redis will show all the commands executed by the server like in the following example: * Stopped at 1, stop reason = step over It will stop at the first line of the script that actually does something before executing it.įrom this point you usually call step in order to execute the line and go to the next line. Note that when you start the debugger it will start in stepping mode. Redis.breakpoint() Stop execution as if there was a breakpoint in the bug() Produce logs in the debugger console. In syncĭebugger functions you can call from Lua scripts: Reak - Remove breakpoint from the specified line.Įval Execute some Lua code (in a different callframe).Īxlen Trim logged Redis replies and Lua var dumps to len.Ībort Stop the execution of the script. Reak Add a breakpoint to the specified line. Rint Show the value of the specified variable. List In this form specifies how many lines List List source code around current line.
0 Comments
Leave a Reply. |