Opp repl sanitizer tests

Skill tabgab/opp_repl-skill/opp-repl-sanitizer-tests

Run simulations built with AddressSanitizer / UBSan instrumentation to catch memory errors and undefined behavior. Uses the `sanitize` build mode. Load when hunting down flaky crashes, UAFs, leaks, or UB that normal release builds miss.From its SKILL.md

Install

npx -y skills add tabgab/opp_repl-skill --skill opp-repl-sanitizer-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 446 tokens by cl100k_base, as published. Nobody here has run it

Sanitizer tests

Sanitizer tests build the simulation with AddressSanitizer and UndefinedBehaviorSanitizer (sanitize build mode) and run it. Any detected issue is captured in stderr and reported as an ERROR.

Upstream reference: https://github.com/omnetpp/opp_repl/blob/main/doc/sanitizer_tests.md

Python API

run_sanitizer_tests(simulation_project=inet_project)

# Scope + longer CPU budget (sanitizer builds are slow)
run_sanitizer_tests(simulation_project=inet_project,
                    working_directory_filter="examples/ethernet",
                    cpu_time_limit="10s")

Command line

opp_run_sanitizer_tests --load inet.opp -p inet

Cost model

Sanitizer binaries run 2x-10x slower and use more memory. Keep cpu_time_limit tight and scope to affected areas. Nightly CI is a better fit than per-commit runs.

Interpreting failures

When ASAN reports, the error text appears in the result's stderr. print_stderr() on the failing TaskResult dumps it. Typical patterns:

heap-use-after-free / heap-buffer-overflow -- memory lifetime bug in a C++ module.
undefined-behavior from UBSan -- signed overflow, misaligned access, invalid enum cast, etc.
runtime error: load of null pointer -- dereferencing a NULL pointer during cleanup.

Pitfalls

Compiler and sanitizer-runtime versions affect output format; keep the toolchain stable across baseline and CI.
Some third-party libraries leak on purpose; suppress via LSAN_OPTIONS=suppressions=... when running.
Sanitizer builds cannot be used for speed tests or coverage — each is a separate build mode.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.