Sven Sauleau

@sterlingwes could you please go on https://deploy.workers.cloudflare.com, clear your browser's cache / cookies and try the deploy button again? the fields should show up.

Using chrome:  Do you see any errors in the console?

Could you remove the link from the troubleshooting doc and redirect users to the get started guide? So we only have one link and it's the correct one. cc @celso

Indeed, I closed the issue while only half of the work was done. The team is working on it.

@swiing the change is conflicting now. I'm happy to merge it once fixed.

I don't think Wasm coredump should prevent optimizations, given that ideally it's enabled by default. It's not uncommon to see coredump in native environment with missing values because they were...

> The wasm coredump format doesn't seem to allow omitting values that are optimized away Correct, at the moment it doesn't. I'm going to add it, thanks for your input!

https://github.com/WebAssembly/tool-conventions/issues/198 has been closed. The coredump format now allows to mark local/stack values as missing.

I made a change to add initial/basic coredump generation: https://github.com/bytecodealliance/wasmtime/pull/5868. Could you please have a look and let me know if this is the right direction? It uses `WasmBacktrace` for...

Basic coredump generation has been merged (thanks!). Now, to have the complete debugger experience, we need to collect the following information: - Wasm locals of each stack frames - Snapshot...