__wasm_call_ctors can break the interpreter

[MDFL64]

When compiling in debug mode, descriptor functions can generate calls to __wasm_call_ctors, which can cause it to try executing code the interpreter doesn't support. I only started running into this a few months ago on nightly rust builds.

This is admittedly probably my fault for linking with C++ code in a weird way, and not something most users will run in to. I'm not really sure what the best way of dealing with this is. I don't even fully understand why these calls are generated, and why only in debug mode. The bodge I've implemented is to just skip executing functions with this name, which feels very dumb.

I wasn't super enthusiastic about setting up a project to reproduce this, but I can on request.

[alexcrichton]

Oh dear, thanks for the report! Were you perhaps compiling for the wasm32-wasi target though? If though I think wasm32-unknown-unknown will be your best bet for working with wasm-bindgen.