Hi Maxim, > Are these full backtraces you got from ASan? If so, do you use stripped > libraries on your system (on Ubuntu, I guess, you do). Could this issue > (https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00132.html) be related to to > your problem?
Maybe part of the intermediate solution is to provide asan_symbolize since we have a partial work around. I suggest it because I know these compiler problems can be a bear to track down. If you want to provide use asan_symbolize for situations like these, then I suggest either (1) running 2to3 on it; or (2) changing shebang to '/usr/bin/env python2' . If you run 2to3 on it, then test it. There will be two or three minor issues to fix. Also see http://github.com/google/sanitizers/issues/372. I attached asan_symbolize from the LeMaker HiKey. Jeff
asan_symbolize.tar
Description: Unix tar archive
_______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
