Am 22.10.13 14:24, schrieb Christoph Badura: > On Tue, Oct 22, 2013 at 09:25:19AM +0100, Alexander Nasonov wrote: >> We just need to make sure that all entry points to Lua are protected and >> hope that the above panic will never trigger. > > Actually, I would prefer if that call to panic wasn't there at all. > Instead the script/state should be aborted noisily. I absolutely agree. A problem within a Lua state must not cause a kernel panic. The only way to panic from Lua should be calling "core.panic()" explicitely.
- Re: CVS commit: src/sys/modules/lua Marc Balmer
- Re: CVS commit: src/sys/modules/lua Jukka Ruohonen
- Re: CVS commit: src/sys/modules/lua Taylor R Campbell
- Re: CVS commit: src/sys/modules/lua Marc Balmer
- Re: CVS commit: src/sys/modules/lua Alan Barrett
- Re: CVS commit: src/sys/modules/lua Izumi Tsutsui
- Re: CVS commit: src/sys/modules/lua Alexander Nasonov
- Re: CVS commit: src/sys/modules/lua Alexander Nasonov
- Re: CVS commit: src/sys/modules/lua Christoph Badura
- Re: CVS commit: src/sys/modules/lua Alexander Nasonov
- Re: CVS commit: src/sys/modules/lua Marc Balmer
- Re: CVS commit: src/sys/modules/lua Alan Barrett
- Re: CVS commit: src/sys/modules/lua Alexander Nasonov
- Re: CVS commit: src/sys/modules/lua Lourival Vieira Neto
- Re: CVS commit: src/sys/modules/lua Alexander Nasonov
- Re: CVS commit: src/sys/modules/lua Lourival Vieira Neto
