Skip to content
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

Open
kazcw opened this issue May 27, 2022 · 0 comments
Open

debug=true vs debug=1 #274

kazcw opened this issue May 27, 2022 · 0 comments

Comments

@kazcw
Copy link

kazcw commented May 27, 2022

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, however debug=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 to wasm-pack is 3.3GB with debug=true. With debug=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 by debug=true is useful in some way, mention the difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant