Skip to content
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

Alternative for wasmer inspect #1554

Open
svanimpe opened this issue May 12, 2024 · 1 comment
Open

Alternative for wasmer inspect #1554

svanimpe opened this issue May 12, 2024 · 1 comment

Comments

@svanimpe
Copy link

I'm trying to use wasm-tools to reproduce the clear and concise overview produced by wasmer inspect. For example (abbreviated):

$ wasmer inspect module.wasm
Type: wasm
Size: 14.5 MB
Imports:
  Functions:
    "javascript_kit"."swjs_i64_to_bigint": [I64, I32] -> [I32]
    "javascript_kit"."swjs_bigint_to_i64": [I32, I32] -> [I64]
    "javascript_kit"."swjs_set_subscript": [I32, I32, I32, I32, F64] -> []
  Memories:
  Tables:
  Globals:
Exports:
  Functions:
    "_initialize": [] -> []
    "__main_argc_argv": [I32, I32] -> [I32]
    "swjs_call_host_function": [I32, I32, I32, I32] -> [I32]
    "swjs_free_host_function": [I32] -> []
  Memories:
    "memory": not shared (81 pages..)
  Tables:
  Globals:

Is this currently possible with wasm-tools?

@alexcrichton
Copy link
Member

The wasm-tools CLI doesn't have anything that can directly produce this output, but is there any particular part of the output you're most interested in? This output is sort of similar to wasm-tools print | grep of sorts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants