lua/testes/db.lua, branch v5.4.9 A mirror of https://github.com/lua/lua https://git.lua4.win/lua/atom?h=v5.4.9 2024-05-13T16:10:35+00:00 Bug: Active-lines for stripped vararg functions 2024-05-13T16:10:35+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2024-05-13T16:10:35+00:00 urn:sha1:dfbde4c7d540f81f2cc539741a2c1f4c00f91c10 Lua seg. faults when asked to create the 'activelines' table for a vararg function with no debug information. More control over encoding of test files 2023-08-17T13:42:56+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-08-17T13:42:56+00:00 urn:sha1:f4211a5ea4e235ccfa8b8dfa46031c23e9e839e2 The few UTF-8 test files are commented as such, and there is only one non UTF-8 test file (to test non UTF-8 sources). Small improvements in tests 2023-05-15T13:20:13+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2023-05-15T13:20:13+00:00 urn:sha1:c197885cb00b85251c35cffdc4057efaee2d7a88 Avoid excessive name pollution in test files 2022-12-28T21:34:11+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-12-28T21:34:11+00:00 urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6 Test files are more polite regarding the use of globals when locals would do, and when globals are necessary deleting them after use. Fix debug information about finalizers 2021-12-14T15:50:05+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-12-14T15:50:05+00:00 urn:sha1:066e0f93c4901e601d93e31fb700f8f66f95feb8 The flag CIST_FIN does not mark a finalizer, but the function that was running when the finalizer was called. (So, the function did not call the finalizer, but it looks that way in the stack.) Wrong assert in 'collectvalidlines' 2021-11-25T13:11:05+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-11-25T13:11:05+00:00 urn:sha1:48835c76c8df62fab4827a9835b351718d20df4b Avoid OP_VARARGPREP for active lines 2021-11-10T18:07:14+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-11-10T18:07:14+00:00 urn:sha1:e8deac5a41ffd644aaa78fda6d4bd5caa72cb077 when building the table 'activelines' for a vararg function, this first instruction does not make the first line active. Bug: cannot allow the call 'debug.getinfo(0, ">")' 2021-02-15T13:38:09+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-02-15T13:38:09+00:00 urn:sha1:38cc7d40a4bcb89314d212fdffd2ca8deebc3cb7 A 'what' argument starting with '>' indicates that there is a function in the C stack, which won't be there if the first argument is not a function. Better error messages for calling non-callable objects 2020-12-29T16:15:54+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2020-12-29T16:15:54+00:00 urn:sha1:4bd10b6fe81c0a56eb9e01e24fba10e655966870 When available, use the calling code to find a suitable name for what was being called; this is particularly useful for errors of non-callable metamethods. This commit also improved the debug information for order metamethods. Fixed wrong trace of vararg functions 2020-10-19T18:55:25+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2020-10-19T18:55:25+00:00 urn:sha1:e4a38eb0e828e9589c391171e2e1904a3b9698e7 Trace of vararg functions was skipping an instruction when returning from a call. (Bug introduced by commit 5d8ce05b3.)