tree 30675f9c3872133a1148fff88c01284becbb9318
parent f7bd9700c034d80c43a040318c84d1d7682be5ac
author Sebastian Poeplau <poeplau@code-intelligence.com> 1620399633 -0700
committer Copybara-Service <copybara-worker@google.com> 1620612673 -0700

[libFuzzer] Fix stack overflow detection

Address sanitizer can detect stack exhaustion via its SEGV handler, which is
executed on a separate stack using the sigaltstack mechanism. When libFuzzer is
used with address sanitizer, it installs its own signal handlers which defer to
those put in place by the sanitizer before performing additional actions. In the
particular case of a stack overflow, the current setup fails because libFuzzer
doesn't preserve the flag for executing the signal handler on a separate stack:
when we run out of stack space, the operating system can't run the SEGV handler,
so address sanitizer never reports the issue. See the included test for an
example.

This commit fixes the issue by making libFuzzer preserve the SA_ONSTACK flag
when installing its signal handlers; the dedicated signal-handler stack set up
by the sanitizer runtime appears to be large enough to support the additional
frames from the fuzzer.

Reviewed By: morehouse

Differential Revision: https://reviews.llvm.org/D101824

GitOrigin-RevId: 70cbc6dbef7048d3b1aa89a676d96c6ba075b41b