obs-testing-guide

To debug an OBS Studio plugin crash, set up a debug build, attach a debugger like GDB or LLDB, and analyze memory issues using tools like AddressSanitizer or Valgrind.

Yes, you can write unit tests for OBS plugins written in Rust using `cargo test`, while C/C++ plugins can be tested using custom harnesses to verify individual components.

The best way to log variables inside an OBS Studio plugin is using the built-in `blog()` function, which captures runtime information for debugging and integrated testing.

Yes, AddressSanitizer works with C++ OBS Studio plugins to detect memory errors, and you can complement it with Valgrind for deeper memory checks during testing.

You set up a test environment for OBS plugin development by configuring a debug build, integrating testing frameworks like `cargo test` or custom harnesses, and utilizing OBS's `blog()` logging for integrated testing.

Use Valgrind when debugging OBS plugins to perform comprehensive memory checks and detect leaks or invalid memory access that might not surface during standard unit testing.