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
Currently we reject minidumps in which some modules have garbled code_files outright. It would be better to stackwalk the rest of the minidump and just skip the offending modules. To this end, we would need to:
Log an error when we encounter an invalid code_file (this already happens)
Display some placeholder string like <invalid> or <corrupted> in the UI
Replace the useless name with None in derived types that perform lookups based on the code_file
The text was updated successfully, but these errors were encountered:
Currently we reject minidumps in which some modules have garbled
code_file
s outright. It would be better to stackwalk the rest of the minidump and just skip the offending modules. To this end, we would need to:code_file
(this already happens)<invalid>
or<corrupted>
in the UINone
in derived types that perform lookups based on thecode_file
The text was updated successfully, but these errors were encountered: