Re: nCcalls in the global state keeps increasing in 5.2

[Roberto Ierusalimschy <roberto@...>]

> BTW, I noticed that nCcalls is not reset (unwind) if the Lua parser throws
> an error when nCcalls > 200 and a Lua error function is installed. I made
> some test code that kept on recursing until nCcalls > 200. An error was
> thrown and the error function executed, which also failed due to nCcalls
> being too large. I removed the error handler and nCcalls was correctly
> unwind.

Note that nCcalls should unwind only after the error handler runs (after
all, when the handler runs the stack is still large), so this failure is
correct. But are sure it is not begin unwound after that (that is, when
lua_pcall returns)?

-- Roberto