On 2018/05/31 15:47, Marco van Hulten wrote:
> whereas calcurse stops in rthread.c, which I thought could be a
> calcurse bug so I reported it [1], but I'm not sure at all anymore.
>
> [1]: https://lists.calcurse.org/bugs/msg00261.html
The gdb output there doesn't include anything that will help track
things down. At least a backtrace is needed ("bt" at the gdb prompt),
but there will be more information included in the backtrace if you
build from ports like this
pkg_delete calcurse
cd /usr/ports/productivity/calcurse
make clean
make DEBUG=-g repackage
make install
Since it's threaded you might get something more useful with
"thread apply all bt full".
Normally I'd suggest reporting to the port maintainer first
(perhaps CC ports@openbsd.org) and see if they have an idea,
but since it's already reported upstream it would be good to
followup there with the backtrace as well.
No comments:
Post a Comment