Debugging rust/wasm32 infinite loops

I have a Rust/wasm32 app.
It compiles fine.
When I run it, Chrome hits 100%, and nothing is displayed.
[This is likely due to an infinite loop somewhere.]

Without inserting console!(log, ...) everywhere, is there a way to "C-c break" or "force inject a panic!()" so that the app halts and dumps the typical backtrace that panic!() would dump?

Code is compiled with target=wasm32-unknown-unknown.


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.