iwasm doesn't respect timeout in start function execution

[sjamesr]

Let's say you run

iwasm --timeout=4000 foo.wasm

If foo.wasm has a start function with an infinite loop (e.g. due to a bug), the intepreter is not able to interrupt execution after 4 seconds. The interpreter will try to interrupt modules by calling wasm_runtime_terminate, but this requires a module instance, and obviously in this case module instantiation cannot finish.

What do you all think of adding some mechanism to interrupt the start function after a period of time? Is there a way to do this that I'm missing?

[lum1n0us]

🤔 Something like #2163 and #3927