Try a build with ASSERTIONS too, that might help. If the game works without safe heap, which is possible, then this might be ok to ignore - like if it writes to an invalid address, but it never tries to read it back.
Otherwise, the only thing to do is investigate that constructor, and maybe add some debugging logging code to see what's going on - is it reading/writing from 0? or doing an unaligned access? Then need to find out where the bad pointer came from, etc. On Mon, Aug 8, 2016 at 5:32 PM, caiiiycuk <[email protected]> wrote: > Hi! I try to update old emscripten branch of cocos2d to work with latest > emscripten. And for now i can run sample projects of cocos2d with latest > emscripten. But i have problem with SAFE_HEAP, if i set SAFE_HEAP=1 then > sample game throws segfault. I can`t see anything intresting in stacktrace, > just 3 lines with constructor calls. Constructors are very simple - > primitive field initialization. How i can investigate the problem. When i > use SAFE_HEAP_LOG then browser hangs up. It is possible that program will > work normally with SAFE_HEAP=0? > > Thank you. > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
