Wenyong Huang

@bnason-nf the method of this PR in the AOT mode will allocate memory for the global instances, which increases footprint and the binary size. How about we define the `wasm_global_inst_t`...

Hi, maybe you can refer to the assembly-script sample in wamr-app-framework repo: https://github.com/bytecodealliance/wamr-app-framework/tree/main/assembly-script Here it defines [Console APIs](https://github.com/bytecodealliance/wamr-app-framework/tree/main/assembly-script#console-apis) for `console.log` and `console.log_number`, which are implemented in: https://github.com/bytecodealliance/wamr-app-framework/blob/main/assembly-script/wamr_app_lib/console.ts

Hi, could you try defining macro BUILTIN_LIBC_BUFFERED_PRINTF and enlarging the buffer size with macro BUILTIN_LIBC_BUFFERED_PRINT_SIZE? It only outputs the buffer when `\n` is met or the buffer is full: https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/core/iwasm/libraries/libc-builtin/libc_builtin_wrapper.c#L348-L386

Yes, moving buffer inside str_context is good, and the text losing may be caused by some remaining characters without '\n' are not dumped. I tried to refactor the code, could...

Welcome. #3460

Hi, for the first one, could you check whether the native method is called successfully (e.g. add a printf in the native method), and whether the exception is thrown when...

It is a little confusing that it runs good in Ubuntu while failed in your environment. What target and what platform do you use? And did you create another exec_env...

In the thread created by method A, should not call wasm_runtime_init and wasm_runtime_init_thread_env again since they have been inited. Could you try removing them?

Don't remove wasm_runtime_init_thread_env in ThreadLoadWasm as the thread is not created by runtime, and ensure that wasm_runtime_destroy_thread_env is called before ThreadLoadWasm returns. And keep removing wasm_runtime_init and wasm_runtime_destroy int ThreadLoadWasm...

No, if the thread is to run a function of the same module instance that the thread belongs to, I think we had better use `wasm_runtime_spawn_thread`, otherwise had better create...