How to debug android native crash with anonymous and unknown backtrace?

That I completely understand, but what I do not understand is how that applies to complex types like c3b?

How can cc.c3b(0, 0, 0) be nil, since it’s a valid object, as is cc.c3b(255, 255, 255). They are neither nil, nor false. Wouldn’t local color = cc.c3b(0, 0, 0) or cc.c3b(255, 255, 255) result in undefined behavior (which is what you seem to be experiencing)?

c3b is a function defined in Cocos2d.lua which returns a table.

function cc.c3b( _r,_g,_b )
    return { r = _r, g = _g, b = _b }
end

since table value is not nil or false, the statement local color = cc.c3b(0, 0, 0) or cc.c3b(255, 255, 255) should aways result with cc.c3b(0, 0, 0).
So we wonder is there any problem in that luajit library.

Oh right, so it has nothing to do with the actual values of r,g,b in the c3b object, and you’re simply testing the existence of the object, so local color = cc.c3b(0, 0, 0) or cc.c3b(255, 255, 255) is just a test case.