devs/cproof
1
2
Fork 1
Code Issues 43 Pull Requests 6 Actions Packages Projects 1 Releases Wiki Activity

Merge pull request #2151 from profanity-im/issue

Browse Source 
chore: Explain how to get a backtrace
This commit is contained in:
Michael Vetter
2026-04-13 21:29:09 +02:00
committed by GitHub
parent c071d6cf84 dbc739bcc5
commit 49240083b0
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.github/ISSUE_TEMPLATE/bug_report.md vendored
View File

@@ -35,10 +35,24 @@ assignees: ''
## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
## Backtrace
<!--- In case of a crash attach the backtrace. Otherwise delete this section -->
* 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
* Operating System/Distribution
* glib version
* libstrophe version
* omemo backend
* Some bugs might be due to specific implementation in the server. `/serversoftware example.domain` can be helpful