- 08 Jan, 2016 1 commit
-
-
antirez authored
Example of offending code: > script debug yes OK > eval "local a = {1} a[1] = a\nprint(a)" 0 1) * Stopped at 1, stop reason = step over 2) -> 1 local a = {1} a[1] = a > next 1) * Stopped at 2, stop reason = step over 2) -> 2 print(a) > print ... server crash ... Close #2955.
-
- 16 Dec, 2015 3 commits
-
-
antirez authored
-
Paul Kulchenko authored
-
Paul Kulchenko authored
-
- 27 Nov, 2015 1 commit
-
-
Itamar Haber authored
Fixes #2898
-
- 18 Nov, 2015 1 commit
-
-
antirez authored
-
- 17 Nov, 2015 28 commits
-
-
antirez authored
Thanks to Itamar Haber for bug report and test case to reproduce.
-
antirez authored
Let the user control the replies truncation.
-
antirez authored
-
antirez authored
-
antirez authored
Now it lists code around the current position by default. Can list any other part using other arguments, but a new "whole" command was added in order to show the whole source code easily.
-
antirez authored
"async" -> "sync". Thanks to Itamar Haber for reporting.
-
antirez authored
Thanks to Itamar Haber for reporting.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
When the debugger exits now it produces an <endsession> tag that informs redis-cli (or other debugging clients) that the session terminated. This way the client knows there is yet another reply to read (the one of the EVAL script itself), and can switch to non-debugging mode ASAP.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
It's handly to just eval "5+5" without the return and see it printed on the screen as result. However prepending "return" does not always result into valid Lua code. So what we do is to exploit a common Lua community trick of trying to compile with return prepended, and if compilation fails then it's not an expression that can be returned, so we try again without prepending "return". Works great apparently.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 09 Nov, 2015 1 commit
-
-
antirez authored
Arguments arity and arguments type error of redis.call() were not reported correctly to Lua, so the command acted in this regard like redis.pcall(), but just for two commands. Redis.call() should always raise errors instead.
-
- 05 Nov, 2015 2 commits
- 04 Nov, 2015 1 commit
-
-
Jan-Erik Rediger authored
-
- 30 Oct, 2015 2 commits