Re: uncaught_exceptionv erri

2019-07-09 Thread Stéphane Letz
Yes the -s ASSERTIONS=1 stuff fixes it. Thanks. Le mardi 9 juillet 2019 23:56:49 UTC+2, Alon Zakai a écrit : > > If you are loading the code as an ES6 module, that error looks like it > might be the same as > > > https://github.com/emscripten-core/emscripten/pull/8306#discussion_r284040606 > >

Re: The state of debugging c++

2019-07-09 Thread Alon Zakai
Source maps are the closest thing currently: build with -g4, load in a browser's devtools, and you should see the original C++ source code, and can place breakpoints. However, variable names don't work. That will need something more like DWARF, which people are currently working on. On Wed, Jul

Re: uncaught_exceptionv erri

2019-07-09 Thread Alon Zakai
If you are loading the code as an ES6 module, that error looks like it might be the same as https://github.com/emscripten-core/emscripten/pull/8306#discussion_r284040606 which was pulled off into https://github.com/emscripten-core/emscripten/issues/8678 As a workaround until that is fixed,

Re: C++ main loop and browser events

2019-07-09 Thread Alon Zakai
A "while (1) " loop is not valid on the web. Was that loop pasted in there by mistake? The "SimulateInfiniteLoop" exception is part of how emscripten fakes an infinite loop. It is thrown because you pass "1" as the last param to that set_main_loop call,

Re: Strange error in EMCC compiled code

2019-07-09 Thread J Decker
https://github.com/emscripten-core/emscripten/issues/8774 On Tue, Jul 9, 2019 at 6:19 AM Stéphane Letz wrote: > We get this error when using C++ code compiled with EMCC 1.38.31 > > ReferenceError: tempDouble is not defined > at Object.doStat (http:// >

Strange error in EMCC compiled code

2019-07-09 Thread Stéphane Letz
We get this error when using C++ code compiled with EMCC 1.38.31 ReferenceError: tempDouble is not defined at Object.doStat (http://127.0.0.1:8000/libwasm-worklet-glue.js:4848:46) at ___syscall197 (http://127.0.0.1:8000/libwasm-worklet-glue.js:6494:23) at _fstat

Re: Getting emscripten's header files

2019-07-09 Thread Mehdi Sabwat
Hi, I use emsdk to manage the versions of the toolchain I use: https://github.com/emscripten-core/emsdk when you execute emcc, it will look for what's in emscripten/system/include so you can easily #include or (look into emscripten/system/include for the full list of headers) On Tuesday,

Getting emscripten's header files

2019-07-09 Thread שחר לנגבהיים
Hi, I didn't find the best practices regarding including emscripten.h and html5.h in a project. Most of the examples I see just copy the files into the project, but that means that the only way to receive updates is to copy them manually. What's the best way to use emscripten's headers? Add it

Re: 32-bit SDK of Emscripten 1.38.x

2019-07-09 Thread Manuel Häusler
If I see it right the logic in gnu/stubs.h is responsible for the selection of the header file: #if !defined __x86_64__ # include #endif #if defined __x86_64__ && defined __LP64__ # include #endif #if defined __x86_64__ && defined __ILP32__ # include #endif Therefore I conclude from this

Re: 32-bit SDK of Emscripten 1.38.x

2019-07-09 Thread Beuc
You can't use your system (i386) headers for an Emscripten (asmjs/wasm) application :) If JModelica can't be compiled without i386 headers (AFAIU), it probably can't compiled for the asmjs/wasm target. You'll need to improve JModelica so it supports more targets/architectures. Cheers! Beuc On