badgermole

Results 7 comments of badgermole

Support try-catch in Asyncify / lower wasm exceptions to MVP

> There are two modes, see https://emscripten.org/docs/porting/exceptions.html > > Basically the old mode is `-fexceptions`. It works with Asyncify (but there might be bugs). The new mode is `-fwasm-exceptions`. That...

Support try-catch in Asyncify / lower wasm exceptions to MVP

Thanks very much @caiiiycuk, I wish I could.

trace.h dead?

> I have the time, so I'll submit a PR that removes this. :) I've also just spent a bit of time trying to get tracing to work (tried Address...

With a pthread build, and bundled with webpack, creation of new Web Worker fails due to protocol=file: in import.meta.url

I was thrilled when I saw #22165 because I was having the same issue, and that did resolve it in that case. So a qualified 'yes' to `does #22165 fix...

With a pthread build, and bundled with webpack, creation of new Web Worker fails due to protocol=file: in import.meta.url

You're right. That and the file: protocol getting used for import.meta.url led me to exclude my.js from the webpack bundle, putting it in the same directory as my.wasm. But that...

With a pthread build, and bundled with webpack, creation of new Web Worker fails due to protocol=file: in import.meta.url

I apologize for neglecting this - I had to switch tasks for a bit. I appreciate your comments and questions up to this point. I should also try opening an...

With a pthread build, and bundled with webpack, creation of new Web Worker fails due to protocol=file: in import.meta.url

> I've added some basic testing of threads with webpack rollup and vite ([#23753](https://github.com/emscripten-core/emscripten/pull/23753)). I think we still lack coverage of your specific case here, but we are making progress....