search

rustwasm / book

The Rust and WebAssembly Book
https://rustwasm.github.io/docs/book/
MIT License
1.75k stars 211 forks source link

Document that backtraces can be mangled and to use another browser if there are issues #222

Open aidanhs opened 4 years ago

aidanhs commented 4 years ago

Where in the docs did you come across this?

https://rustwasm.github.io/docs/book/reference/debugging.html#logging-panics

Describe what about it does not make sense

The instructions indicate the first step in getting a backtrace printed, but don't indicate what to do if the output is garbled:

(example possibly due to the file being too large for firefox? not sure

Panic location: <::std::macros::panic macros>:2 inline841.js:1:108
    __cargo_web_snippet_72fc447820458c720c68d0d8e078ede631edd723 http://localhost:8765/snippets/stdweb-bb142200b065bd55/inline841.js:1
    __wbg_cargowebsnippet72fc447820458c720c68d0d8e078ede631edd723_ece3da0a4474dbeb http://localhost:8765/geehorus_page.js:478
    logError http://localhost:8765/geehorus_page.js:237
    hce2f2d4e22155d74 http://localhost:8765/geehorus_page.js line 349 > WebAssembly.instantiate:2623185
    h74822b39e74a421f http://localhost:8765/geehorus_page.js line 349 > WebAssembly.instantiate:3030873
    h23eb2234b796013f http://localhost:8765/geehorus_page.js line 349 > WebAssembly.instantiate:3107018
    hbb9227beea098a96 http://localhost:8765/geehorus_page.js line 349 > WebAssembly.instantiate:1602817
[...]

)

How could we improve it?

Suggest to use another browser (e.g. chrome) if the backtraces are garbled