Sigil version 0.7.4 for OSX crashes on startup.
I have just upgraded from version 0.7.2 to 0.7.4 via a download of
Sigil-0.7.4-Mac-Package.dmg.
I verified the MD5 signature in terminal and installed Sigil in /Applications.
On startup Sigil crashes with a segmentation violation. Here's the crash log
from Console:
Process: launchd [69587]
Path: /Applications/Sigil.app/Contents/MacOS/Sigil
Identifier: com.sigil-ebook.Sigil.app
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [143]
Date/Time: 2014-03-16 23:51:03.011 +0000
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 1
Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 3627
thread_create: 0
thread_set_state: 0
What steps will reproduce the problem?
On my machine just running the application crashes it immediately.
What is the expected output?
The program running.
What do you see instead?
A crash report.
What version of the product are you using?
Sigil 0.7.4
On what operating system?
Mac OSX 10.7.5 (11G63)
Steven Docker
Original issue reported on code.google.com by steven.d...@gmail.com on 17 Mar 2014 at 12:09
Original issue reported on code.google.com by
steven.d...@gmail.com
on 17 Mar 2014 at 12:09