Try if you can come up with a smaller test case that extracts the bug, which you can then post publicly without exposing your own source code.
Also, try building with the "-s SAFE_HEAP=1" linker flag. This adds extra checks for unaligned memory accesses which are not supported, and can cause random silent failures when running. 2014-06-09 14:48 GMT+03:00 Stanislav Tsukrov <[email protected]>: > Hi! > > I'm trying to port a project to JS with EMScripten. > In one place JS seems to output a different value than a clang compiled > executable. > > I think there's a bug in JS-backend. > How can I post an issue without sharing the closed sources to everybody? > Whom should I contact? > > One note: trying to printf some temporary values results in correct output. > It looks like Emscripten mess up some pseudo-registers or something like > that. > > Tried to use autodebugger, but I don't know how to build the libc for it. > > -- > 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.
