Displaying 2 results from an estimated 2 matches for "__asan_report_".
2019 Sep 12
3
Requesting clarification of some HWASAN behaviours.
Hello,
I'm working on implementing hwasan instrumentation in GCC, and have just
started discussing my current work-in-progress on the gcc-patches
mailing list.
(https://gcc.gnu.org/ml/gcc-patches/2019-09/msg00387.html -- the email
that Kostya saw and added people to).
I've gotten about as basic a user-space implementation as possible
(using the interceptor ABI) up and running, and would
2019 Sep 20
2
Extra questions about HWASAN
...t;
> I'm a little uncomfortable putting architecture specific assembly code
> into the mid-end of GCC (even though the entire HWASAN is AArch64
> specific in GCC) and would like to put some "just report" functions into
> libhwasan (in the same manner that libasan has
> `__asan_report_(load|store){1,2,4,8,16,_n}{,_noabort}` functions).
>
> Would that be OK? It's a simple patch that I already have locally. I
> guess tag-mismatch reporting would then contain an extra function in the
> stack report?
Does __hwasan_tag_mismatch / __hwasan_tag_mismatch_stub work for...