You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In bug 1861359, yannis is seeing evidence of a mismatch between a module on disk and a module in memory at the time of a crash and the minidump contains module information where the version doesn't match the code id. This leads to symbolicated stacks that are nonsense because we unwind and symbolicate with the wrong symbols file.
In order to detect this situation, it would help to include the Windows module version in an INFO line in the generated symbols file. Then the stackwalker could compare the version from the symbols file with what's in the module list stream in the minidump when processing a crash report and cry out in despair at the universe when there is a mismatch.
Maybe something like this?:
INFO MODULE_VERSION 115.0.3esr
The text was updated successfully, but these errors were encountered:
In bug 1861359, yannis is seeing evidence of a mismatch between a module on disk and a module in memory at the time of a crash and the minidump contains module information where the version doesn't match the code id. This leads to symbolicated stacks that are nonsense because we unwind and symbolicate with the wrong symbols file.
In order to detect this situation, it would help to include the Windows module version in an
INFO
line in the generated symbols file. Then the stackwalker could compare the version from the symbols file with what's in the module list stream in the minidump when processing a crash report and cry out in despair at the universe when there is a mismatch.Maybe something like this?:
The text was updated successfully, but these errors were encountered: