compare(new_output, old_output); report.store(test_case); } generate_summary_report();20 Aurora Innovation Snapshot Testing Debugging System is treated as a black box. Output may miss important data. Reliability test_case: test_suite) { auto new_output = new_system(test_case); store_snapshot(test_case, new_output); auto old_output = load_snapshot(test_case); auto report = compare(new_output, old_output); report Debugging Good tests point to the root cause when they fail.22 Aurora Innovation Problem: Reliability Snapshot tests are prone to capturing non-deterministic data. are prone to capturing unimportant data.

/ AddressSanitizer / memcheck massif snapshot in the end VS. snapshots over timeMemory Leaks: Tools TestAllocator / AddressSanitizer / memcheck massif snapshot in the end VS. snapshots over time LEAK 669 blocks Memory Leaks: Tools TestAllocator / AddressSanitizer / memcheck massif snapshot in the end VS. snapshots over time LEAK SUMMARY: definitely lost: 921,664 bytes in 730 blocks

Victor Ciura | @ciura_victor - 2020: The Year of Sanitizers? Snapshot File Game changer! Minidump file (*.dmp) <= Windows snapshot process (program virtual memory/heap + metadata) VS can parse general ➡ + Live Share76 2020 Victor Ciura | @ciura_victor - 2020: The Year of Sanitizers? Snapshot Loaded77 2020 Victor Ciura | @ciura_victor - 2020: The Year of Sanitizers? How does it work

issues: information overload; profiling overhead (skew) selective (manual) Sampling callstack snapshot probing system-wide automatic (regular intervals) OS kernel events hardware counters issues: issues: information overload; profiling overhead (skew) selective (manual) Sampling callstack snapshot probing system-wide automatic (regular intervals) OS kernel events hardware counters issues:

issues: information overload; profiling overhead (skew) selective (manual) Sampling callstack snapshot probing system-wide automatic (regular intervals) OS kernel events hardware counters issues: issues: information overload; profiling overhead (skew) selective (manual) Sampling callstack snapshot probing system-wide automatic (regular intervals) OS kernel events hardware counters issues:

Executor Support ● 33.2 Safe Reclamation ○ 33.2.1 Hazard Pointers ○ 33.2.2 RCU ○ 33.2.3 Latest/Snapshot? ○ 33.2.4 Asymmetric fences 15 © 2021. 16 To learn or not to learn? • What did we learn? • What

deterministic execution when the simulator is configured to run in synchronous mode: while (true) { get_snapshot(); for (sensor : all_sensors) { sensor.update(); // storing all messages that would be sent

(VBS) ○ Intel Software Guard Extensions (Intel SGX)Fuzzing ● LibFuzzer + Address Sanitizer ● Snapshot Fuzzing (Nyx, What the Fuzz) ● Structure Aware Fuzzing (libprotobuf-mutator) ● Fuzzing as a Service

🔥 🚫 🚫 React / Recover / Control2021 Victor Ciura | @ciura_victor - Exceptional C++ 23 Snapshot - context 🔎 📸 SEH2021 Victor Ciura | @ciura_victor - Exceptional C++ 24 CONTEXT struct

need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe using the locked versions for both libb/0.2@user/testing and liba/0.1@user/testing, as this was the snapshot of existing versions when the CI pipeline started, even if later a liba/0.2@user/testing was created