> I'm strongly against the blacklist, > that is not the way things are done in GCC, > you have corresponding attribute to mark functions > you don't want to instrument, people can macroize that with > __typeof (symbol) symbol __attribute__((__no_sanitize_address__)); > But in any case, you mark it in the code rather than > adding externally some symbol list.
I think the functionality in question is not specific for Asan. In general it may be useful to allow control of compiler options at intra-file level with the help of external config (blacklist file in this case). I can imagine situations where people would prefer to avoid changing their codes and simply throw in a config. As Kostya pointed out you sometimes can't change 3rd party codes.
-Y
