mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Note impact of -Cstrip on backtraces

Browse Source 
It is not always clear to people what the impact of `-Cstrip` options are.
They are a common question on sites like StackOverflow, and sometimes
people even report bugs with "no backtrace" after deliberately mangling
the symbol table. We cannot exhaustively document every permutation, but
we should warn people about common effects.
This commit is contained in:
Jubilee Young 2024-04-01 12:44:49 -07:00
parent a7e3b1c8c5
commit 3896f07627
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/doc/rustc/src/codegen-options/index.md
View File

@ -553,9 +553,12 @@ Supported values for this option are:
of MSVC). of MSVC).
- `debuginfo` - debuginfo sections and debuginfo symbols from the symbol table - `debuginfo` - debuginfo sections and debuginfo symbols from the symbol table
section are stripped at link time and are not copied to the produced binary 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 - `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 ## symbol-mangling-version