[PATCH] [Sanitizers] Order initialization of coverage and guard arrays

Evgeniy Stepanov eugenis at google.com
Mon Jan 26 06:18:43 PST 2015


There is actually a bigger problem here: if __sanitizer_cov_module_init runs before __asan_init (and that's possible since they are at the same priority), we will fail to activate asan, in particular - we won't update coverage and coverage_dir from activation flags.

I think the right fix would be reverting this change and lowering the priority of the coverate module initializer to 2 (keeping __asan_init at 1).


REPOSITORY
  rL LLVM

http://reviews.llvm.org/D6892

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/






More information about the llvm-commits mailing list