-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to determine module name? #261
Comments
Looks like
|
There are some open design questions concerning the naming of modules, such as this. The "!!! no export named __wasi_memory, or the export isn't a mem: None" error message is admittedly confusing. It would say "memory" instead of "__wasi_memory". I've now opened #264 to fix that. That said, what this error message means is that if you're using WASI, you're currently required to have a memory export named "memory", because many WASI functions expect to be able to access it. That's independent of any other exports you have. |
I have read the discussion in the proposal. Looks like this feature haven't been standardized yet. Is there anything that still calls for participation? It would be wonderful if I can contribute even a little thing. I would like to know if you have any helpful suggestion to help me find out any alternative way to achieve my goal. Here's what I plan to do. Briefly, I want to implement a tool to do the interposition-like job on Linux dynamic linking for either debugging or profiling. Let's say I have a In my opinion, the only left option is to do it in the linking stage. Using |
I believe the concerns here should be addressed by the |
I try to use
preload
option to load a function out of the main module and it keeps showing this error message.How to know runtime the exported wasm file's module name?
The text was updated successfully, but these errors were encountered: