Scribe - Reporting Crashes

Sitemap

Home Blog Forums FAQ YouTube Email

Reporting Crashes in Scribe

If Scribe crashes it will usually generate a crash dump. These are needed to see where the crash occured so it's important to send them to me along with any crash report.

The things that I need in a crash report are:

Windows

If you get an "Application Crash"...
This application has crashed. A mini dump has been written to: ... Take careful note of the path to the crash dump. On modern windows it will be:
C:\Users\username\AppData\Roaming\Scribe\Scribe-#,##,##,##-crash.dmp
But on Windows XP it should be:
C:\Documents And Settings\username\Application Data\Scribe\Scribe-#,##,##,##-crash.dmp
If you have trouble getting to the AppData folder, just type it into the path bar like this.

Then find the latest .dmp file: And send it to me. Once you have sent me the file, you can delete it.

Mac

If you get "Scribe quit unexpectedly"... Open Finder and from the Go menu select "Go To Folder..." And enter the name: ~/Library/Logs/DiagnosticReports

In that folder there should be some crash dump files starting with "Scribe": Send me that file(s) and then delete any old reports. Please include the version of Scribe you are running and what version of OS X you are using.

Leave any files not starting with "Scribe" alone.

Linux

To debug a crash on Linux first you have to turn on core dumps. So open a terminal and enter these commands:
Change directory to where Scribe is installed: 
user@linux:~$ cd ~/Downloads/scribe-linux-v2.1.42
Set the ulimit to allow core files: 
user@linux:~/Downloads/scribe-linux-v2.1.42$ ulimit -c unlimited
Now run the application from the terminal: 
user@linux:~/Downloads/scribe-linux-v2.1.42$ ./scribe
And do whatever until the software crashes. Then a core file should be creating in the current folder. Check that it's there: 
user@linux:~/Downloads/scribe-linux-v2.1.42$ ls -l
total 67232
drwxrwxr-x 3 user user     4096 Apr 27 21:17 Aspell
-rw------- 1 user user 53665792 Apr 29 09:04 core
drwx--x--x 2 user user     4096 Apr 29 09:02 Folders.mail3
drwxrwxr-x 3 user user     4096 Apr 27 21:17 Help
-rwxrwxr-x 1 user user  1949444 Apr 27 21:17 libaspell-dist-060.so
-rwxrwxr-x 1 user user  5418474 Apr 27 21:17 liblgi.so
drwxrwxr-x 2 user user     4096 Apr 27 21:17 Resources
-rwxrwxr-x 1 user user  7775069 Apr 27 21:17 scribe
-rw------- 1 user user     1957 Apr 29 09:02 ScribeOptions.bak
-rw------- 1 user user     2017 Apr 29 09:02 ScribeOptions.xml
-rw------- 1 user user     1557 Apr 29 09:04 scribe.txt
drwxrwxr-x 2 user user     4096 Apr 29 09:02 Scripts
At this point just zip up the core file and send it to me or host it somewhere (e.g. Dropbox or Google Drive) and send me a link.

Alternatively you could do a stack trace for me and send me that instead: 
user@linux:~/Downloads/scribe-linux-v2.1.42$ gdb ./scribe ./core
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
...snip...
Reading symbols from ./scribe...(no debugging symbols found)...done.
[New LWP 16676]
[New LWP 16723]
[New LWP 16753]
[New LWP 16818]
[New LWP 16726]
[New LWP 16743]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./scribe'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000060ea8d in ScribeWnd::OnCommand(int, int, Gtk::_GtkWidget*) ()
Then to get the stack trace type in 'bt': 
(gdb) bt
#0  0x000000000060ea8d in ScribeWnd::OnCommand(int, int, Gtk::_GtkWidget*) ()
#1  0x00007fbad5c802dd in GView::OnEvent(GMessage*) () from ./liblgi.so
#2  0x0000000000610e7f in ScribeWnd::OnEvent(GMessage*) ()
#3  0x00007fbad5c80ec6 in GWindow::OnGtkEvent(Gtk::_GtkWidget*, Gtk::_GdkEvent*) () from ./liblgi.so
...snip...
(gdb)
Then send me the output from that command.