Today on GitHub a ppc64el webhook was turned on for the systemd project. The fuzzers (built with ASan) crashed there as soon as they started with something like
```
757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1)
--- command ---
/usr/bin/env /tmp/autopkgtest.vdKhS9/build.g6f/systemd/build-deb/fuzz-varlink:address /tmp/autopkgtest.vdKhS9/build.g6f/systemd/test/fuzz/fuzz-varlink/oss-fuzz-14708
--- stderr ---
==24171==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
==24171==ASan shadow was supposed to be located in the [0x01ffffff0000-0x11ffffffffff] range.
==24171==Process memory map follows:
``` https://github.com/systemd/systemd/pull/13568#issuecomment-545426488
I'm not sure what exactly is going on there but I'm wondering if anyone runs anything under ASan on ppc64el on a regular basis. Is it even supported there?
Today on GitHub a ppc64el webhook was turned on for the systemd project. The fuzzers (built with ASan) crashed there as soon as they started with something like oss-fuzz- 14708:address FAIL 0.02 s (exit status 1)
```
757/758 fuzz-varlink:
--- command --- t.vdKhS9/ build.g6f/ systemd/ build-deb/ fuzz-varlink: address /tmp/autopkgtes t.vdKhS9/ build.g6f/ systemd/ test/fuzz/ fuzz-varlink/ oss-fuzz- 14708 -0x11ffffffffff ] range. /github. com/systemd/ systemd/ pull/13568# issuecomment- 545426488
/usr/bin/env /tmp/autopkgtes
--- stderr ---
==24171==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
==24171==ASan shadow was supposed to be located in the [0x01ffffff0000
==24171==Process memory map follows:
```
https:/
I'm not sure what exactly is going on there but I'm wondering if anyone runs anything under ASan on ppc64el on a regular basis. Is it even supported there?