profanity

development blog

How to get a backtrace

Posted at — Jan 26, 2020 by mdosch

When you’re running profanity master it may occur that profanity crashes with SIGSEGV or SIGABRT when new features are added. If this happens it is helpful to provide a backtrace for the developers to find and fix the bug.

I will explain one possibility how to get a backtrace of profanity (or any other TUI application)1:

Preparation

The following requirements must be installed:

Run profanity


  1. This explanation was first published on my personal blog. ↩︎

  2. bt full gives a much more detailled output but in most cases bt is enough for the dev to know what’s going on. ↩︎