From fe0371641f8e2d20ebac5b456589a4794965ba77 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20=C3=85dahl?= Date: Thu, 29 Aug 2024 23:31:36 +0200 Subject: [PATCH] docs/debugging: Update CI reproduction steps No need to manually deal with pipewire or runtime directories anymore. Part-of: --- doc/debugging.md | 21 +++++++-------------- 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/doc/debugging.md b/doc/debugging.md index 23f4583a7..3d3c79768 100644 --- a/doc/debugging.md +++ b/doc/debugging.md @@ -87,21 +87,14 @@ Renderdoc is usually the better tool to debug something with, but it's also hard dnf install -y gdb ``` -4. Replicate a environment and run the test inside gdb. What you need here depends on the test that needs investigation. In the simplest case, the following is enough: +4. Run the test case + + ```sh + meson test -C build failing-test-case + ``` + +5. Run the test case in gdb ```sh - export XDG_RUNTIME_DIR=$PWD/runtime-dir - mkdir -p $XDG_RUNTIME_DIR ./src/tests/meta-dbus-runner.py meson test -C build --setup plain --gdb failing-test-case ``` - - If it involves screen casting, it becomes a bit more complicated: - - ```sh - export XDG_RUNTIME_DIR=$PWD/runtime-dir - mkdir -p $XDG_RUNTIME_DIR - ./src/tests/meta-dbus-runner.py bash -l - pipewire& - wireplumber& - meson test -C build --setup plain --gdb failing-test-case - ```