lua/ldo.c, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92026-07-22T17:42:55+00:00Bug: GC checks stack space before running finalizer2026-07-22T17:42:55+00:00Roberto Iroberto@inf.puc-rio.br2026-07-22T17:42:55+00:00urn:sha1:8511e90b7df5daf139aba290b9c9c1595927e7b3
If some stack does not have a minimum available space, the GC defers
calling a finalizer until the next cycle. That avoids errors while
running a finalizer that the programmer cannot control.
Bug: 'luaD_seterrorobj' should not raise errors2025-03-12T19:01:03+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-03-12T19:01:03+00:00urn:sha1:25da574fcbb68bf507431a6091ab73ac434c9428
This function can be called unprotected, so it should not raise any
kind of errors. (It could raise a memory-allocation error when creating
a message).
Bug: Missing error status in panic function2025-01-16T19:25:11+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-01-16T19:25:11+00:00urn:sha1:f5e55be2a0ce64066c1b0554675633b92c91fafb
'luaD_throw' may call 'luaE_resetthread', which returns an error code
but clears 'L->status'; so, 'luaD_throw' should set that status again.
Bug: Yielding in a hook stops in the wrong instruction2024-01-11T16:44:16+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-01-11T16:44:16+00:00urn:sha1:e288c5a91883793d14ed9e9d93464f6ee0b08915
Yielding in a hook must decrease the program counter, because it already
counted an instruction that, in the end, was not executed. However,
that decrement should be done only when about to restart the thread.
Otherwise, inspecting the thread with the debug library shows it one
instruction behind of where it really is.
Several functions turned 'static'2023-05-22T17:47:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-05-22T17:47:54+00:00urn:sha1:9be74ccc214eb6f4d9d0b9496fd973542c7377d9
Several functions that were already being used only inside their
own file have been declared as 'static'.
Corrected support for 16-bit systems2023-03-09T14:10:04+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-03-09T14:10:04+00:00urn:sha1:1de2f31694ddbc86b18e491c8aedc91791f512e2
We still need access to a 16-bit system to correctly test
these changes.
Stack reallocation done with a single realloc2022-10-31T18:06:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-10-31T18:06:20+00:00urn:sha1:ee645472ebe153e2c6669c84a632297a8110bdb6
To avoid the need of both the old and the new stack addresses valid
at the same time, to correct the pointers to the stack, these pointers
are changed to offsets before the reallocation and then changed back
to pointers after the reallocation.
Stack 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.
More checks and documentation for uses of EXTRA_STACK2022-05-26T18:14:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-05-26T18:14:54+00:00urn:sha1:d61b0c60287c38008d312ddd11724a15b1737f7bBug: '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:196bb94d66e727e0aec053a0276c3ad701500762