On Sun, Apr 22, 2018 at 12:59 AM, Harshith H <[email protected]> wrote:
> HI , > We are trying to apply asan to our custom OS . > There are set of libc functions and standard API'S intercepted . Can > anyone help me with what criteria is used to intercept ? Why not other > functions /methods . > Some functions are *replaced* by asan because asan needs them to behave differently. This is basically malloc and friends. Other functions are intercepted because asan needs to inject extra functionality. E.g. for pthread_create we need to catch when a thread is created. Most other functions are intercepted so that we see memory accesses inside them and report the buggy ones (e.g. memcpy, strcmp, etc) If you control the OS, it's likely better to build asan support into your libc as opposed to intercepting the libc functions on the asan side. --kcc > > > Thank you > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
