sandboxed-api/sandboxed_api/examples/stringop/lib
Christian Blichmann 5c7903ecd9 Check for either violate() or ViolateIndirect() in stack trace
Depending on architecture and optimization level, the compiler may choose to
not generate full stack frames, even with no-inline and no tail-call
attributes.

PiperOrigin-RevId: 372339987
Change-Id: I42043131bbb6092ff234e80ae9047f7a2bf31161
2021-05-06 07:36:13 -07:00
..
BUILD.bazel Make stack trace test more resilient against optimizer 2021-04-29 06:01:24 -07:00
CMakeLists.txt Make stack trace test more resilient against optimizer 2021-04-29 06:01:24 -07:00
sandbox.h Update license header with recommended best practices 2020-01-17 05:05:29 -08:00
stringop_params.proto Update license header with recommended best practices 2020-01-17 05:05:29 -08:00
stringop.cc Check for either violate() or ViolateIndirect() in stack trace 2021-05-06 07:36:13 -07:00