lua

A copy of the Lua development repository
Log | Files | Refs | README

commit 969b8c1f14f69c1406f00df3b5f375a9efb7b78f
parent c65605151c5a335baf0a9ea251b19df5b2d3a905
Author: Roberto Ierusalimschy <roberto@inf.puc-rio.br>
Date:   Fri, 26 Apr 2019 11:12:34 -0300

Fixed bug with to-be-closed variables in base C level

To-be-closed variables in C use 'ci.nresults' to code that there is
a variable to be closed in that function. The intialization of the
base C level (the one "running" when calling API functions outside
any Lua call) did not initialize 'ci.nresults', creating (correct)
warnings in valgrind.

Diffstat:
Mlstate.c | 2++
1 file changed, 2 insertions(+), 0 deletions(-)

diff --git a/lstate.c b/lstate.c @@ -196,6 +196,8 @@ static void stack_init (lua_State *L1, lua_State *L) { ci->next = ci->previous = NULL; ci->callstatus = CIST_C; ci->func = L1->top; + ci->u.c.k = NULL; + ci->nresults = 0; setnilvalue(s2v(L1->top)); /* 'function' entry for this 'ci' */ L1->top++; ci->top = L1->top + LUA_MINSTACK;