This has all got very confusing and somewhere this issue got associated with the OpenCV issue. There are 3 issues being discussed 1) This uncaught type error, 2) Linking problem 3) OpenCV Crash. I will start new topics for my 2 problems.
John On Monday, 28 October 2019 21:56:29 UTC, Alon Zakai wrote: > > These seem to be separate issues: > > > Uncaught (in promise) TypeError: o[r[((r[(w2 >> 2)] + 8) >> 2)]] is not > a function > > That looks like a wasm2js error perhaps, assuming that is using wasm2js > (non-WASM output on 1.39.0, by default). Does using latest-fastcomp fix > that for you? And does it work in wasm mode? > > It would be good to get a testcase of this. Even a large one might be > enough to debug it (I'd just build with wasm and without, and compare the > diff in the behavior). > > (In general, this "not a function" issue is likely a bad function pointer > call, which may be due to memory corruption or something else bad.) > > > Compiled code throwing an exception > > That is a C++ language exception being thrown, like maybe an assertion > failed in cvRegisterType. It would be interesting to know if using fastcomp > and/or wasm affects that too. > > - Alon > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/90a9536f-8b3a-4b51-9de4-a34d09f3ee79%40googlegroups.com.
