fix: Write STACK WIN records correctly #513
Merged
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.
The structure of STACK WIN records is described in https://github.com/google/breakpad/blob/master/docs/symbol_files.md#stack-win-records. In particular:
has_program_string
flag should beFrameData
(type 4) records:1
if the record has a program string,0
otherwise;FPO
(type 0) records: always0
.FrameData
records: the program string if it exists, empty otherwise;FPO
records:1
if the frame pointer register is used as a general-purpose register,0
otherwise.However, this is not what the current code does; we instead unify
has_program_string
anduses_base_pointer
into one flag. Kudos to rust-minidump for discarding the resulting invalid records and logging this fact.