Repository navigation
chore(build): build debug info as line tables - #566
Open
LKSNDRTMLKV wants to merge 1 commit into
Open
LKSNDRTMLKV wants to merge 1 commit into
LKSNDRTMLKV wants to merge 1 commit into
Conversation
LKSNDRTMLKV
added
the
no-changelog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Debug and test builds now keep only line tables as debug info:
[profile.dev] debug = "line-tables-only".Backtraces and panic messages keep their function names, files and line numbers. What goes is the variable-level DWARF, which is most of a debug
target/and most of the memory a test-binary link needs. The cost is inspecting variables in a step debugger.testinherits fromdev, so the test binaries are covered too.Only this workspace's own builds read the profile. A crate that depends on these crates from crates.io builds them under its own profile, so nothing published changes.
Related issue
None. Found while tracing disk and memory pressure on a 15 GiB development machine.
Changes
Cargo.toml: a[profile.dev]section, with a comment saying what it keeps and what it costs.Measured
Each run:
just checkfrom an emptytarget/in the same worktree, under the same CPU and memory cap. The first row is unchangedmain(58c6e1e), the second is this branch.target/target/debug/depsmain)line-tables-onlyThe wall time is indicative only: other builds were running on the machine. Both gates were green. This branch's gate ran 2,121 tests, all passing.
Checklist
just checkpasses locally.envfiles in the diffno-changeloglabel, and a reason belowNo changelog: a development build-profile change; no published crate or document changes.