Hi Rob,
I believe the following diff against Mobdebug 0.606 should fix the
issue and I'd appreciate if you could give it a try:
diff --git a/lualibs/mobdebug/mobdebug.lua b/lualibs/mobdebug/mobdebug.lua
index 7829ed0..751a532 100644
--- a/lualibs/mobdebug/mobdebug.lua
+++ b/lualibs/mobdebug/mobdebug.lua
@@ -642,6 +642,7 @@ local function debug_hook(event, line)
-- return something else (for example, 'exit'), which needs to be handled
if status and res and res ~= 'stack' then
if not abort and res == "exit" then os.exit(1, true); return end
+ if not abort and res == "done" then mobdebug.done(); return end
abort = res
-- only abort if safe; if not, there is another (earlier) check inside
-- debug_hook, which will abort execution at the first safe opportunity
@@ -907,7 +908,7 @@ local function debugger_loop(sev, svars, sfile, sline)
-- do nothing; it already fulfilled its role
elseif command == "DONE" then
server:send("200 OK\n")
- done()
+ coroyield("done")
return -- done with all the debugging
elseif command == "STACK" then
-- first check if we can execute the stack command
I tested it with Lua 5.1, 5.2, and LuaJIT and it seems to work as
expected. Thank you.
Paul.
On Fri, Oct 10, 2014 at 11:58 AM, Rob Probin<rob.probin@xxxxxxxxx> wrote:
No problem. If you need anything else, let me know.
On 10 Oct 2014, at 00:31, Paul K<paul@xxxxxxxxxxxxx> wrote:
Hi Rob,
Are you using Lua 5.1, 5.2, or LuaJIT?
Lua 5.2.2
Just a brief update; I've been able to reproduce this issue with Lua
5.2 and have been working on investigating and fixing it, but no
solution yet.
Paul.
