diff options
| author | Jens Peters <jp7677@gmail.com> | 2022-06-24 17:45:20 +0300 |
|---|---|---|
| committer | Jens Peters <jp7677@gmail.com> | 2022-06-24 17:45:20 +0300 |
| commit | ccb4f6c615bcd6407c3746c0837616aaad5fc521 (patch) | |
| tree | 63122ee7ac6598769649fa4c801d26ab22cfc3b8 | |
| parent | 8db165050c67327f67451849dfe7d99faf684008 (diff) | |
meta: Add instructions for debugging the test suite
| -rw-r--r-- | README.md | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -88,6 +88,18 @@ The test executable also runs on Windows against NVIDIA's `nvapi64.dll`. Ensure The actual unit tests can be run with `nvapi64-tests.exe [@unit-tests]` to validate DXVK-NVAPI's internal implementation. +Producing a debug build and starting a debugging session with the test suite can be achieved with the following snippet: + +```bash +meson --cross-file "./build-win64.txt" --buildtype "debug" -Denable_tests=True builddir && cd builddir +meson compile + +ln -sr src/nvapi64.dll tests/nvapi64.dll # to ensure that nvapi64-tests.exe finds nvapi64.dll +DXVK_LOG_LEVEL=none DXVK_NVAPI_LOG_LEVEL=none WINEDEBUG=-all WINEDLLOVERRIDES=nvapi64=n winedbg --gdb tests/nvapi64-tests.exe [@all] +``` + +Once the debug session has started, use `c` to start/continue execution and a.o. `bt` to show a proper stacktrace after a segmentation fault. + ## References and inspirations - [DXVK](https://github.com/doitsujin/dxvk) |