This is an archive of the discontinued LLVM Phabricator instance.

sanitizer_common: be more verbose, when symbolizer is not found.
ClosedPublic

Authored by krasin on Oct 27 2015, 3:25 PM.

Details

Summary

I have othen been stuck when I got an ASAN report, but no symbols
are resolved. The reasons might be different, and it always
requires a bit of detective work to track down.

These more verbose error messages will help the users like me.

Diff Detail

Event Timeline

krasin updated this revision to Diff 38604.Oct 27 2015, 3:25 PM
krasin updated this revision to Diff 38605.
krasin retitled this revision from to sanitizer_common: be more verbose, when symbolizer is not found..
krasin updated this object.
krasin added a reviewer: samsonov.
krasin added a subscriber: llvm-commits.

.

Alexey,

friendly ping!

samsonov added inline comments.Oct 28 2015, 11:44 AM
lib/sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc
386

This is sort of inconsistent - we use VReport(2) if ASAN_OPTIONS=symbolize=0 is used, for example.

465

Don't you need to print error message only if symbolizer list is empty? E.g. it's perfectly fine if we weren't able to find external symbolizer, but internal symbolizer (which takes precedence) is used.

krasin updated this revision to Diff 38678.Oct 28 2015, 12:01 PM

reduce scope

PTAL

lib/sanitizer_common/sanitizer_symbolizer_posix_libcdep.cc
386

Removed for now.

465

That's a good idea. I didn't quite realize the process of the symbolizer selection. Please, take another look. Is it better now?

samsonov accepted this revision.Oct 28 2015, 1:45 PM
samsonov edited edge metadata.

LGTM

This revision is now accepted and ready to land.Oct 28 2015, 1:45 PM
krasin closed this revision.Oct 28 2015, 1:47 PM