From 741777d2c768876349234693ea7ccad4b3962ffa Mon Sep 17 00:00:00 2001 From: Michael Vetter Date: Mon, 13 Apr 2026 13:12:28 +0200 Subject: [PATCH] chore: Explain how to add a backtrace in issue template Signed-off-by: Michael Vetter --- .github/ISSUE_TEMPLATE/bug_report.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index b554ac1d..c3d13e1a 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -35,6 +35,19 @@ assignees: '' ## Context +## Backtrace + +* Install gdb and gdbserver: For example on openSUSE `zypper in gdb gdbserver` +* Open two terminals. +* Terminal 1: Start gdbserver `gdbserver localhost:port path/to/profanity` e.g. `gdbserver localhost:1234 ./build_run/profanity` +* Terminal 2: Start gdb `gdb path/to/profanity` e.g. `gdb ./build_run/profanity` +* Terminal 2: Attach to server `target remote localhost:port` e.g. `target remote localhost:1234` +* Terminal 2: Enable logging to file `set logging enabled on` and `set logging file my.log` +* Terminal 2: Type `c` +* Terminal 1: Use profanity to reproduce the crash +* Terminal 2: Show the backtrace `bt` or `bt full` +* Copy the backtrace here, either from gdb or from your logfile (`my.log`) + ## Environment * Give us the version and build information output generated by `profanity -v` * If you could not yet build profanity, mention the revision you try to build from