diff options
| author | Brian Ashworth <RedSoxFan@users.noreply.github.com> | 2018-12-17 12:42:49 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-17 12:42:49 -0500 |
| commit | 0d741782c4451e0cde5ab0b4fa09470000d1ca57 (patch) | |
| tree | 646ee8d97368b544664b9cfa76d1f7aa5be441cf | |
| parent | 4e2cfe0526e1278abc9c7370e62a4dbdc4a9c63c (diff) | |
| parent | 4a42561a6282d013a3532f8eb05cf177d6918467 (diff) | |
| download | sway-0d741782c4451e0cde5ab0b4fa09470000d1ca57.tar.xz | |
Merge pull request #3305 from emersion/isue-template-stack-trace
issue template: add instructions for stack traces
| -rw-r--r-- | ISSUE_TEMPLATE.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md index 5f3bb6bb..7caa5d1e 100644 --- a/ISSUE_TEMPLATE.md +++ b/ISSUE_TEMPLATE.md @@ -5,7 +5,7 @@ If you are using the nvidia proprietary driver for any reason, you have two choi If `lsmod | grep nvidia | wc -l` shows anything other than zero, your bug report is not welcome here. -Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. +Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. If sway crashes, also include a stack trace. Obtain your version like so: @@ -32,3 +32,11 @@ You should try to reproduce the issue with the default configuration. If you can * Configuration File: Finally, explain the steps you took in plain English to reproduce the problem below. + +* Stack Trace, if sway crashes: + +If you use systemd, you should be able to open the coredump of the most recent crash with GDB like so: + + coredumpctl gdb sway + +And then type `bt full` to obtain the stack trace. |