-
Notifications
You must be signed in to change notification settings - Fork 205
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
debug=true
vs debug=1
#274
Comments
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Where in the docs did you come across this?
https://rustwasm.github.io/book/reference/debugging.html#building-with-debug-symbols
Describe what about it does not make sense
The book recommends using
debug=true
so that symbol information will be available in stack traces, howeverdebug=1
seems to be sufficient for informative stack traces.Why does it not make sense?
I'm working on a project where the intermediate WASM file passed from
rustc
towasm-pack
is 3.3GB withdebug=true
. Withdebug=1
, the same file is 0.5GB. This difference corresponds to more than a factor of 2 difference in build times in a common incremental case.How could we improve it?
Recommend
debug=1
; or if the extra data produced bydebug=true
is useful in some way, mention the difference.The text was updated successfully, but these errors were encountered: