lua/lfunc.h, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92022-10-29T15:06:37+00:00Stack indices changed to union's2022-10-29T15:06:37+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-10-29T15:06:37+00:00urn:sha1:413a393e6222482f46599e138bebac162610a572
That will allow to change pointers to offsets while reallocating
the stack.
Bug: 'lua_settop' may use an invalid pointer to stack2022-05-25T20:41:39+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-05-25T20:41:39+00:00urn:sha1:196bb94d66e727e0aec053a0276c3ad701500762New implementation for to-be-closed variables2021-02-09T17:00:05+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-09T17:00:05+00:00urn:sha1:4e47f81188d37e29027158b76271d02a781242e2
To-be-closed variables are linked in their own list, embedded into the
stack elements. (Due to alignment, this information does not change
the size of the stack elements in most architectures.) This new list
does not produce garbage and avoids memory errors when creating tbc
variables.
Allow yields inside '__close' metamethods2021-01-13T16:54:10+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-01-13T16:54:10+00:00urn:sha1:b07fc10e91a5954254b47280aba287220c734a4b
Initial implementation to allow yields inside '__close' metamethods.
This current version still does not allow a '__close' metamethod
to yield when called due to an error. '__close' metamethods from
C functions also are not allowed to yield.
Cleaner handling of errors in '__close' metamethods2020-12-28T14:40:30+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-12-28T14:40:30+00:00urn:sha1:7af27ef59da4051914d93d8b63efac663b64765a
Instead of protecting each individual metamethod call, protect the
entire call to 'luaF_close'.
Details2019-11-18T17:54:06+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-11-18T17:54:06+00:00urn:sha1:5f83fb658206d195e54d3574b989ce5285a5b18fDo not collect open upvalues2019-07-22T12:41:10+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-22T12:41:10+00:00urn:sha1:9e6807c3c9d5036e999f636f936df07b72284442
Open upvalues are kept alive together with their corresponding
stack. This change makes a simpler and safer fix to the issue in
commit 440a5ee78c8, about upvalues in the list of open upvalues
being collected while others are being created. (That previous fix
may not be correct.)
Fixed bug for emergency collection in upvalue creation2019-07-19T15:13:00+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2019-07-19T15:13:00+00:00urn:sha1:440a5ee78c8592230780310c9c8d8c2ba1700cb1
When creating an upvalue, an emergency collection can collect the
previous upvalue where the new one would be linked. The following
code can trigger the bug, using valgrind on Lua compiled with the
-DHARDMEMTESTS option:
local x; local y
(function () return y end)();
(function () return x end)()
New functions 'lua_resetthread' and 'coroutine.kill'2018-12-13T15:07:53+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2018-12-13T15:07:53+00:00urn:sha1:fdc25a1ebfe9968dcec390dd556375105aa0be40
New functions to reset/kill a thread/coroutine, mainly (only?) to
close any pending to-be-closed variable. ('lua_resetthread' also
allows a thread to be reused...)
Handling of memory errors when creating to-be-closed upvalues2018-10-18T19:15:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2018-10-18T19:15:09+00:00urn:sha1:3c7dc52909ce0688bdb20cacaf686413a79aaf48