diff options
| author | Roberto I <roberto@inf.puc-rio.br> | 2026-07-12 14:57:55 -0300 |
|---|---|---|
| committer | Roberto I <roberto@inf.puc-rio.br> | 2026-07-12 14:57:55 -0300 |
| commit | b996f8fd1be7fb711cc6f754a31a1c87d2c2fd9b (patch) | |
| tree | 575dd4819e9fbf7e7696908cf779b6f55825f181 /testes/bitwise.lua | |
| parent | bc4bbcef651ba2870d6c68db16dc7d6ce6f68636 (diff) | |
| download | lua-b996f8fd1be7fb711cc6f754a31a1c87d2c2fd9b.tar.gz lua-b996f8fd1be7fb711cc6f754a31a1c87d2c2fd9b.tar.bz2 lua-b996f8fd1be7fb711cc6f754a31a1c87d2c2fd9b.zip | |
Bug: Issues with write barrier for __newindex
In 'luaV_finishset', there is an update on a table that is a field on
another table. If the first table is the same as the one with the field
(e.g., after 't.__newindex = t'), the update can change the value on
that field (e.g., there may be a collision and the field is moved, or
the field being updated is '__newindex' itself). After that, the
barrier is called with the table stored in that field, which is not
the correct table anymore.
Diffstat (limited to 'testes/bitwise.lua')
0 files changed, 0 insertions, 0 deletions