From d56c0372f5fb4e248949dd576caee34b9ef81ad8 Mon Sep 17 00:00:00 2001 From: Brenden Matthews Date: Mon, 15 Apr 2024 13:16:07 -0400 Subject: [PATCH] Issue template: Link docs to obtain stack traces --- .github/ISSUE_TEMPLATE/bug_report.yml | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 65e6f02ab..48e24d52a 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -1,7 +1,7 @@ name: 🐞 Bug Report -description: "File a bug report: crashes, unexpected behaviour, and other errors go here." -title: "[Bug]: " -labels: ["bug", "triage"] +description: 'File a bug report: crashes, unexpected behaviour, and other errors go here.' +title: '[Bug]: ' +labels: ['bug', 'triage'] body: - type: markdown attributes: @@ -68,6 +68,14 @@ body: # ... stack trace output here ... ``` + + Here are some additional resources on obtaining stack traces: + - [Arch Linux Wiki](https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces) + - [Ubuntu Wiki](https://wiki.ubuntu.com/DebuggingProgramCrash) + - [AskUbuntu - Where do I find core dump files, and how do I view and analyze the backtrace (stack trace) in one?](https://askubuntu.com/a/1349048) + - [Julia Evans - How to get a core dump for a segfault on Linux](https://jvns.ca/blog/2018/04/28/debugging-a-segfault-on-linux/) + - [GDB Documentation](https://sourceware.org/gdb/current/onlinedocs/gdb/) + - [lldb Documentation](https://lldb.llvm.org/use/tutorial.html) - type: textarea id: stacktrace attributes: