lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


In Lua 5.3.5, the VM occasionally looked at L->hookmask inside of
tight loops to determine whether to run the hook function. In Lua
5.4.0-rc3, it now looks at ci->u.l.trap instead. The problem here is
that there's a bunch of ci's, and if you're unlucky, you might not
update all of them. A comment on the settraps function says that in
this case, "the worst that can happen is that the signal will not
interrupt the script." Well, that's pretty bad if you wanted to set a
hook as a timeout to guard against code running an infinite loop. Am I
understanding this correctly? If so, is there a way to mitigate this?
Also, what was the purpose of that change?

Joseph C. Sible
_______________________________________________
lua-l mailing list -- lua-l@lists.lua.org
To unsubscribe send an email to lua-l-leave@lists.lua.org