Bug#935889: tilda: sometimes crashes with int3

[Simon McVittie]

Control: reassign -1 tilda
Control: tags -1 + moreinfo
Control: retitle -1 tilda: sometimes crashes with int3

On Tue, 27 Aug 2019 at 12:02:30 +0200, Peter Kosa wrote:
> program tilda crashes some times causing loosing work in progress which is not expected. Lines from /var/log/messages:
> 
> Aug 21 10:19:31 ******** kernel: [ 9247.740012] traps: tilda[1861] trap int3 ip:7f0a9f6cac75 sp:7ffe363fc610 error:0 in libglib-2.0.so.0.5800.3[7f0a9f692000+7e000]

On x86, GLib crashes with int3 when it is asked to crash because a fatal
error is detected (for example when code that uses GLib calls g_error(),
which is similar to abort()). This has some minor advantages over using
abort(), but when not debugging it is effectively the same.

This probably indicates a bug in either tilda or some GLib-based library
that tilda uses. Please look at the systemd journal or /var/log/syslog
for error messages. Obtaining a backtrace from the crash would probably
also be useful: see <https://wiki.debian.org/HowToGetABacktrace> for more
details.

This might be the same bug as <https://bugs.debian.org/893858>, or it
might be a different bug.

Please send details of tilda and the libraries it uses to this bug report.
You can get those details by running "reportbug --template tilda".

In the Debian bug tracking system it is often best to report crashes as a
bug in the program that crashed, even if you suspect that the root cause
is really in some library that the program uses, so that the bug report
has full details of the program and all of the libraries it uses. Program
maintainers can reassign bugs to libraries if the root cause of the bug
turns out to be in a library.

    smcv