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:
The following requirements must be installed:
gdbserver localhost:1234 /usr/bin/profanity
target remote localhost:1234
bt full 2