Re: PATCH: fixes bug with calling garbage collector from custom lua_Alloc

["Bogdan Marinescu" <bogdan.marinescu@...>]

I was recommended this set of tests:

http://shootout.alioth.debian.org/gp4sandbox/benchmark.php?test=all&lang=lua&lang2=lua

Technically benchmarks, but they should stress Lua hard enough to find
hidden problems.

On Sun, May 4, 2008 at 6:48 AM, Robert G. Jakabosky
<bobby@sharedrealm.com> wrote:
> On Saturday 03, Louis Mamakos wrote:
>  > Do you need to worry about the memory allocator being invoked during a
>  > GC call, and recursively invoking lua_gc() again?
>  My new patch protects against calling luaC_fullgc() recursively.  There might
>  still be a problem if a single GC step (with luaC_step) is happening and the
>  allocator tries to do a full GC.
>
>
>  > Is is possible that a _gc metamethod that might be invoked could
>  > allocate memory in the process of running the method and freeing
>  > up storage and causing a recursive invocation of lua_gc()?
>  I haven't tested the __gc metamethod yet, but as long as the luaC_step &
>  luaC_fullgc functions are protected from recursively call each other, there
>  shouldn't be a problem.
>
>  --
>  Robert G. Jakabosky
>