Thread: core dump
View Single Post
Old 11-09-2017, 09:40 AM   #8
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,643
Karma: 5433388
Join Date: Nov 2009
Device: many
Also simply launching sigil via gdb and running doing a backtrace after the crash/abort would certainly help us to see what might be going on. It should be an easy add to the script that launches sigil after setting the right environment variables.

If not, we could/should add a command line switch to the sigil launch script to enable running it through gdb just to make bug reports from Linux users easier to get given the huge number of different Linux variants.

What do you think?
KevinH is offline   Reply With Quote