MobileRead Forums - View Single Post

KevinH · 04-02-2015, 01:27 PM

Hi Camelot,

Are you familiar with gdb and are you willing to try running Sigil from inside gdb to generate a crash report.

Simply edit (as root or sudo) /usr/local/bin/sigil and change this line:

Code:

 exec /usr/local/share/sigil/sigil-real "$@"

to be (assuming you have gdb installed in /usr/bin)

Code:

 exec /usr/bin/gdb /usr/local/share/sigil/sigil-real "$@"

Then fire up sigil as normal and at the gdb prompt enter:

Code:

run

When it crashes, gdb will appear and use the following to generate a backtrace:

Code:

bt

and copy and paste it here. When done, enter

Code:

 quit

to exit gdb.

Alternatively, you should be able to enable crash (core) dumps on your system by doing the following before starting up sigil.

Code:

ulimit -c unlimited

Getting a backtrace via gdb from a crash dump (core file) would at least give us some idea of where to start looking.

Thanks,

KevinH

04-02-2015, 01:27 PM	#11
KevinH Sigil Developer Posts: 8,541 Karma: 5703586 Join Date: Nov 2009 Device: many	Hi Camelot, Are you familiar with gdb and are you willing to try running Sigil from inside gdb to generate a crash report. Simply edit (as root or sudo) /usr/local/bin/sigil and change this line: Code: exec /usr/local/share/sigil/sigil-real "$@" to be (assuming you have gdb installed in /usr/bin) Code: exec /usr/bin/gdb /usr/local/share/sigil/sigil-real "$@" Then fire up sigil as normal and at the gdb prompt enter: Code: run When it crashes, gdb will appear and use the following to generate a backtrace: Code: bt and copy and paste it here. When done, enter Code: quit to exit gdb. Alternatively, you should be able to enable crash (core) dumps on your system by doing the following before starting up sigil. Code: ulimit -c unlimited Getting a backtrace via gdb from a crash dump (core file) would at least give us some idea of where to start looking. Thanks, KevinH Last edited by KevinH; 04-02-2015 at 01:45 PM.