diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | README.md | 8 |
2 files changed, 5 insertions, 4 deletions
@@ -1,3 +1,4 @@ +build builddir .idea/** .vscode/** @@ -91,11 +91,11 @@ The actual unit tests can be run with `nvapi64-tests.exe [@unit-tests]` to valid 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 "debugoptimized" -Denable_tests=True builddir && cd builddir -meson compile +meson --cross-file "./build-win64.txt" --buildtype "debugoptimized" -Denable_tests=True build/dev +meson compile -C build/dev -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] +ln -sr build/dev/src/nvapi64.dll build/dev/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 build/dev/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. |