Let the users of SymbolizationLoop define a function that produces the list of .dSYM hints (possible path to the .dSYM bundle) for the given binary.
Because the hints can't be added to an existing llvm-symbolizer process, we spawn a new symbolizer process ones each time a new hint appears.
Those can only appear for binaries that we haven't seen before.
Details
Details
- Reviewers
earthdok
Diff Detail
Diff Detail
Event Timeline
Comment Actions
https://codereview.chromium.org/728233003/diff/1/tools/valgrind/asan/asan_symbolize.py contains an example of using this new functionality.
projects/compiler-rt/lib/asan/scripts/asan_symbolize.py | ||
---|---|---|
86 | Why not --dsym-hint? (for consistency) |
projects/compiler-rt/lib/asan/scripts/asan_symbolize.py | ||
---|---|---|
86 | Done. |
projects/compiler-rt/lib/asan/scripts/asan_symbolize.py | ||
---|---|---|
364 | s/this hint/all of the hints for this binary/ | |
371 | Whoa whoa, let's tune the C++ down a bit :P dsym_hints = set(self.dsym_hint_producer(binary)) use_last_symbolizer = bool(dsym_hints - self.dsym_hints) self.dsym_hints |= dsym_hints Also I suggest to rename this to dsym_hints_for_binary. |
Comment Actions
lgtm w/nit
projects/compiler-rt/lib/asan/scripts/asan_symbolize.py | ||
---|---|---|
368 | this belongs inside the if block |
Why not --dsym-hint? (for consistency)