Re: heap-buffer-overflow found in luaG_errormsg

[Jinwei Dong <jwdong2000@...>]

Flyer31 Test wrote:

> Not "good", but I think with iterated print and string functions the

> Lua user generally should be very careful... .

>

> Have a look how print is programmed... print is easy to use, but it

> somehow has to create a larger buffer for this, and iterating this too

> much can for sure get critical.

 

Thanks, I've learned a lot about optimizing the print function on very low resource devices! I think the beauty of Lua is that anyone can use it in a highly customizable way.

 

But this problem doesn't seem to be caused by print, as replacing print with another built-in function will also trigger a crash.

 

Such as:

-----------------------

type(

    xpcall((0),

        function(...)

            local f

            if d[type(type(type(type(t[...]))))] then

            end

        end

    )

)

-----------------------