Skip to content

Note impact of -Cstrip on backtraces #123336

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Apr 2, 2024
Merged

Note impact of -Cstrip on backtraces #123336

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3896f07
Note impact of `-Cstrip` on backtraces
workingjubilee Apr 1, 2024
973663d
Discourage stripping symbols in devtools
workingjubilee Apr 1, 2024
4994f73
Revise strip-symbols paragraph
workingjubilee Apr 1, 2024
1dcaf70
Note -Cstrip is not a security measure
workingjubilee Apr 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions src/doc/rustc/src/codegen-options/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -553,9 +553,12 @@ Supported values for this option are:
of MSVC).
- `debuginfo` - debuginfo sections and debuginfo symbols from the symbol table
section are stripped at link time and are not copied to the produced binary
or separate files.
or separate files. This should leave backtraces mostly-intact but may make
using a debugger like gdb or lldb ineffectual.
- `symbols` - same as `debuginfo`, but the rest of the symbol table section is
stripped as well if the linker supports it.
stripped as well if the linker supports it. On platforms which depend on the
binary's symbol table for backtraces, this can affect them so negatively as to
make the trace completely incomprehensible.

## symbol-mangling-version

Expand Down