-
Notifications
You must be signed in to change notification settings - Fork 824
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
add basic coredump generation #3626
Conversation
WOW. The PR ended being way simpler than I was imagining. I'll review it on Monday with @ptitSeb |
38f573f
to
bc17c8f
Compare
Hey @xtuc, could you also add a documentation file on how to use wasm-coredump with wasmer? (end to end) Thanks! |
@syrusakbary yes sure. This is what I wrote for wasmtime: https://github.com/bytecodealliance/wasmtime/blob/db931d7a93208738b8106e8d8c1a4afc8efaca6d/docs/examples-coredump.md. Where's the best place to write such a documentation for wasmer? |
Probably having that markdown doc inside the |
bc17c8f
to
ca04122
Compare
This change adds a basic coredump generation after a WebAssembly trap was entered. The coredump includes rudimentary stack / process debugging information. A new CLI argument is added to enable coredump generation: ``` wasmer --coredump-on-trap=/path/to/coredump/file module.wasm ``` See docs/en/examples-coredump.md. Refs wasmerio#3578
ca04122
to
ed0951f
Compare
@syrusakbary added some docs. |
Looks great, merging. |
This change adds a basic coredump generation after a WebAssembly trap was entered. The coredump includes rudimentary stack / process debugging information.
A new CLI argument is added to enable coredump generation:
Refs #3578