docs/debugging: Update CI reproduction steps
No need to manually deal with pipewire or runtime directories anymore. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3987>
This commit is contained in:
parent
3248798978
commit
fe0371641f
1 changed files with 7 additions and 14 deletions
|
@ -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
|
||||
```
|
||||
|
|
Loading…
Reference in a new issue