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
Symbolize falls back to file offsets for binaries that cannot be open for read. However, binaries that can be opened but have no symbols will fail symbolization completely even though we could use the file offsets in this case.
Failing completely produces unusable backtraces in chromium as the base address isn't known, e.g.
Fallback to using file offsets if no symbol is found, like we do if the
object could not be opened.
This makes backtraces usable even if objects in the trace are stripped,
since the trace can be symbolized by post-processing it with a tool like
asan_symbolize.py.
Note that this is not currently compatible with SymbolizeCallback as
this overwrites the filename in the buffer. The behavior is unchanged
in that case.
Closes: #514
Symbolize falls back to file offsets for binaries that cannot be open for read. However, binaries that can be opened but have no symbols will fail symbolization completely even though we could use the file offsets in this case.
Failing completely produces unusable backtraces in chromium as the base address isn't known, e.g.
If we allow the fallback to file offsets in this case we'd instead get the following:
Which can be symbolized with asan_symbolize.py to get:
Fixing this would be a huge help to projects that must deploy stripped binaries due to space constraints (e.g. Chromecast, Chrome OS).
The text was updated successfully, but these errors were encountered: