Part of http://reviews.llvm.org/D7827. Although we currently always use only one (or zero) symbolizer tool from POSIXSymbolizer, let's prepare a "fallback chain", which will be useful in the planned atos- and dladdr-based symbolizers.
Details
Details
Diff Detail
Diff Detail
Event Timeline
lib/sanitizer_common/sanitizer_symbolizer_internal.h | ||
---|---|---|
31 | You need a SymbolizerTool constructor that would initialize next to nullptr. Also, add a comment here why you need it. | |
lib/sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc | ||
353–354 | Consider just taking IntrusiveList<SymbolizerTool> as an input parameter. Otherwise you:
| |
369 | Why not just return here? | |
389 | ditto |
Comment Actions
LGTM, but please address the comment.
lib/sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc | ||
---|---|---|
354 | IntrusiveList is designed to be a POD, I think it would be easier to just pass it by value and copy it... | |
519 | That is, no need to call to symbolizer_allocator_ here, just IntrusiveList<SymbolizerTool> list; list.clear(); //... return new(symbolizer_allocator_) POSIXSymbolizer(list); |
You need a SymbolizerTool constructor that would initialize next to nullptr. Also, add a comment here why you need it.