<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lua/ltests.c, branch v5.4.9</title>
<subtitle>A mirror of https://github.com/lua/lua
</subtitle>
<id>https://git.lua4.win/lua/atom?h=v5.4.9</id>
<link rel='self' href='https://git.lua4.win/lua/atom?h=v5.4.9'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/'/>
<updated>2025-01-16T19:25:11+00:00</updated>
<entry>
<title>Bug: Missing error status in panic function</title>
<updated>2025-01-16T19:25:11+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2025-01-16T19:25:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=f5e55be2a0ce64066c1b0554675633b92c91fafb'/>
<id>urn:sha1:f5e55be2a0ce64066c1b0554675633b92c91fafb</id>
<content type='text'>
'luaD_throw' may call 'luaE_resetthread', which returns an error code
but clears 'L-&gt;status'; so, 'luaD_throw' should set that status again.
</content>
</entry>
<entry>
<title>Bug: luaL_traceback may need more than 5 stack slots</title>
<updated>2024-06-04T19:40:53+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2024-06-04T19:40:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=2db966fcbf757775c842bc66449d7e697826aa1d'/>
<id>urn:sha1:2db966fcbf757775c842bc66449d7e697826aa1d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Panic functions should not raise errors</title>
<updated>2023-11-24T19:08:55+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2023-11-24T19:08:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=842a83f09caa2ebd4bc03e0076420148ac07c808'/>
<id>urn:sha1:842a83f09caa2ebd4bc03e0076420148ac07c808</id>
<content type='text'>
The standard panic function was using 'lua_tostring', which may raise
a memory-allocation error if error value is a number.
</content>
</entry>
<entry>
<title>"Emergency" new version 5.4.6</title>
<updated>2023-05-02T19:41:43+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2023-05-02T19:41:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=6443185167c77adcc8552a3fee7edab7895db1a9'/>
<id>urn:sha1:6443185167c77adcc8552a3fee7edab7895db1a9</id>
<content type='text'>
'lua_resetthread' is back to its original signature, to avoid
incompatibilities in the ABI between releases of the same version.
New function 'lua_closethread' added with the "correct" signature.
</content>
</entry>
<entry>
<title>Stack indices changed to union's</title>
<updated>2022-10-29T15:06:37+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2022-10-29T15:06:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=413a393e6222482f46599e138bebac162610a572'/>
<id>urn:sha1:413a393e6222482f46599e138bebac162610a572</id>
<content type='text'>
That will allow to change pointers to offsets while reallocating
the stack.
</content>
</entry>
<entry>
<title>Bug: stack overflow with nesting of coroutine.close</title>
<updated>2022-10-25T19:44:06+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2022-10-25T19:44:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=1e64c1391f9a14115b5cc82066dbf545ae73ee27'/>
<id>urn:sha1:1e64c1391f9a14115b5cc82066dbf545ae73ee27</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Details</title>
<updated>2022-10-19T19:29:54+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2022-10-19T19:29:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=14d2803e55f0bbc2b09890a3b30afbb063ec973d'/>
<id>urn:sha1:14d2803e55f0bbc2b09890a3b30afbb063ec973d</id>
<content type='text'>
Some cast operations rewritten to use respective macros.
</content>
</entry>
<entry>
<title>Bug: luaL_tolstring may get confused with negative index</title>
<updated>2021-07-22T16:48:43+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-07-22T16:48:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=439e45a2f69549b674d6a6e2023e8debfa00a2b8'/>
<id>urn:sha1:439e45a2f69549b674d6a6e2023e8debfa00a2b8</id>
<content type='text'>
When object has a '__name' metafield, 'luaL_tolstring' used the
received index after pushing a string on the stack.
</content>
</entry>
<entry>
<title>Stack check in warning function for tests</title>
<updated>2021-03-02T14:35:40+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-03-02T14:35:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=9a2de786de5da862404995ddd3408f7ad3d54ee8'/>
<id>urn:sha1:9a2de786de5da862404995ddd3408f7ad3d54ee8</id>
<content type='text'>
The warning function using for tests need to check the stack before
pushing anything. (Warning functions are not expected to access a
Lua state, therefore they have no preallocated stack space.)
</content>
</entry>
<entry>
<title>New implementation for to-be-closed variables</title>
<updated>2021-02-09T17:00:05+00:00</updated>
<author>
<name>Roberto Ierusalimschy</name>
<email>roberto@inf.puc-rio.br</email>
</author>
<published>2021-02-09T17:00:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/lua/commit/?id=4e47f81188d37e29027158b76271d02a781242e2'/>
<id>urn:sha1:4e47f81188d37e29027158b76271d02a781242e2</id>
<content type='text'>
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.
</content>
</entry>
</feed>
