Displaying 3 results from an estimated 3 matches for "__hwasan_init".
Did you mean:
__asan_init
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
...happens, would the initial call to `prctl` be put in
> libhwasan, or would something like that be done in Bionic? (n.b. this
> call needs to be done for every program since the setting doesn't
> propagate across fork). I have a patch that adds the relevant `prctl`
> call to what `__hwasan_init` does in libhwasan. I do this because I'm
> using a glibc unmodified for hwasan.
I agree, __hwasan_init is the right place for this.
> ---
> I've noticed code around maintaining a thread-specific ring-buffer of
> the stack frames that have been used (recording the PC and SP)...
2020 Jun 22
3
Hardware ASan Generating Unknown Instruction
Hi,
I am trying to execute a simple hello world program compiled like so:
path/to/compiled/clang -o test --target=aarch64-linux-gnu
-march=armv8.5-a -fsanitize=hwaddress
--sysroot=/usr/aarch64-linux-gnu/
-L/usr/lib/gcc/aarch64-linux-gnu/10.1.0/ -g test.c
However, when I look at the disassembly, there is an unknown
instruction listed at 0x2d51c:
000000000002d4c0 main:
2d4c0: ff c3 00 d1