Comment #2 on issue 342 by tetra2...@gmail.com: Segfault in instrumented
programs that use GNU indirect functions.
https://code.google.com/p/address-sanitizer/issues/detail?id=342
For the record, Clang does not support the ifunc attribute yet,
so this is a GCC-only problem.
There is a bug in LLVM Bugzilla about this so it may get to Clang
eventually.
Am I right that the resolver functions themselves aren't marked anyhow
and may reside in a different TU,
so we can't decide to instrument them differently?
Luckily not: "Finally, the indirect function needs to be defined in the
same translation unit as the resolver function" (from
https://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Function-Attributes.html). So
looks like this could be detected by GCC.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to address-sanitizer+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
