From f81b3eef4f539732c6fc9b12de58c773da6edf85 Mon Sep 17 00:00:00 2001 From: Vaxry <43317083+vaxerski@users.noreply.github.com> Date: Mon, 3 Apr 2023 23:47:01 +0100 Subject: [PATCH] docs: update issue guidelines for asan env --- docs/ISSUE_GUIDELINES.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/ISSUE_GUIDELINES.md b/docs/ISSUE_GUIDELINES.md index b8d007c2..57c5e735 100644 --- a/docs/ISSUE_GUIDELINES.md +++ b/docs/ISSUE_GUIDELINES.md @@ -74,9 +74,7 @@ Make sure you're on latest git. Run `git pull --recurse-submodules` to sync ever > Note: The config file used will be `hyprlandd.conf` instead of `hyprland.conf` 2. `cd ~` -3. For your own convenience, launch Hyprland from a tty with the envvar `ASAN_OPTIONS="log_path=asan.log"`: - - If using a wrapper, add `export ASAN_OPTIONS="log_path=asan.log"` in a separate line before the `exec Hyprland` line. - - If launching straight from the tty, execute `ASAN_OPTIONS="log_path=asan.log" ~/path/to/Hyprland` +3. For your own convenience, launch Hyprland from a tty with the envvar `ASAN_OPTIONS="log_path=asan.log" ~/path/to/Hyprland` 4. Reproduce the crash. Hyprland should instantly close. 5. Check out your `~` and find a file called `asan.log.XXXXX` where `XXXXX` will be a number corresponding to the PID of the Hyprland instance that crashed. 6. That is your coredump. Attach it to your issue.