Hi Alon, I'm able to print out the log using printf, but fail to using -g4. only 5 of the source codes are loaded in the browser(small map, tried on firefox and chrome), although the call stack looks good, clicking the codes which belongs to not-included file will jump to strang places of included C codes.
here is my setting, do you have any idea how can I load all the C codes and debug them in the browser? SET EMCC_DEBUG=1 emcc -v main.c blablabla -o ../test/LT/src/libtheora.js -s EXPORTED_FUNCTIONS="['_main','_initEncoder','_getHeader','_encode','_destory']" -s NO_EXIT_RUNTIME=1 -s SAFE_HEAP=1 -s ALLOW_MEMORY_GROWTH=1 -s TOTAL_MEMORY=78643200 -s ASSERTIONS=2 -g3 SET EMCC_DEBUG=0 p.s. there are the new findings: 1) safari and Edge can handle this as well as firefox and x32 chrome, so look like it only happens on X64 chrome. 2) with identical input, output on the X86 chrome will change with/without setting TOTAL_MEMORY, and in either case, the output length and value are all different from the correct one and each other. On Friday, November 6, 2015 at 6:48:09 AM UTC+8, Alon Zakai wrote: > > I also see an error in chrome (all I have is 64-bit). > > But I would recommend reducing this to as small a testcase before filing > it, as otherwise it is not likely to get much attention from the chrome > devs, in my experience. Have you found where in libtheora the problem > happens? > >> >> > -- 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.
