Impossible to install Sophos AntiVirus Mac

Hi UBCinVancouver,

Thanks for the snippet from the crash log. Also thanks for pointing out my typo - definitely you are right about being very careful with the "sudo rm" command.

---

UBCinVancouver wrote:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 000000000000000000 0 + 0
1 libobjc.A.dylib 0x00007fff80f57ff1 call_load_methods + 162
2 libobjc.A.dylib 0x00007fff80f57d31 load_images + 220
3 dyld 0x00007fff5fc03166 dyld::notifySingle(dyld_image_states, ImageLoader const*) + 344
4 dyld 0x00007fff5fc0bced ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 221
5 dyld 0x00007fff5fc0bdb6 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 58
6 dyld 0x00007fff5fc0211a dyld::initializeMainExecutable() + 133
7 dyld 0x00007fff5fc06996 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 2993
8 dyld 0x00007fff5fc016de dyldbootstrap::start(macho_header const*, int, char const**, long) + 811
9 dyld 0x00007fff5fc01052 _dyld_start + 42

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000000015b9c5c00 rcx: 0x00007fffffe00080 rdx: 0x00007fff700bc3f4
rdi: 0x000000015b9518d4 rsi: 0x00007fff834fe1e0 rbp: 0x00007fff5fbfd930 rsp: 0x00007fff5fbfd918
r8: 0x0000000000000000 r9: 0x00000001001fc0a4 r10: 0x000000000000000f r11: 0x0000000000000000
r12: 0x0000000100110ff0 r13: 0x0000000000000000 r14: 0x000000015b9517fa r15: 0x0000000000000001
rip: 0x0000000000000000 rfl: 0x0000000000010206 cr2: 0x0000000000000000

---

In the snippet above the the interesting part is the stack trace for Thread 0 (the thread that crashed). There is no Sophos-specific code in that trace, in fact it appears to be the operating system loader (dyld) that has crashed. Could be bad memory (memory getting corrupted due to h/w issues, leading to a segfault crash) or could be bad software that is randomly misbehaving. Your previous post suggested other apps crashing, does their strack trace look similar? If so, you have a general system problem. Our software is just a victim of some other fundemental problem.

Hi UBCinVancouver,

Thanks for the snippet from the crash log. Also thanks for pointing out my typo - definitely you are right about being very careful with the "sudo rm" command.

---

UBCinVancouver wrote:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 000000000000000000 0 + 0
1 libobjc.A.dylib 0x00007fff80f57ff1 call_load_methods + 162
2 libobjc.A.dylib 0x00007fff80f57d31 load_images + 220
3 dyld 0x00007fff5fc03166 dyld::notifySingle(dyld_image_states, ImageLoader const*) + 344
4 dyld 0x00007fff5fc0bced ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 221
5 dyld 0x00007fff5fc0bdb6 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 58
6 dyld 0x00007fff5fc0211a dyld::initializeMainExecutable() + 133
7 dyld 0x00007fff5fc06996 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 2993
8 dyld 0x00007fff5fc016de dyldbootstrap::start(macho_header const*, int, char const**, long) + 811
9 dyld 0x00007fff5fc01052 _dyld_start + 42

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000000015b9c5c00 rcx: 0x00007fffffe00080 rdx: 0x00007fff700bc3f4
rdi: 0x000000015b9518d4 rsi: 0x00007fff834fe1e0 rbp: 0x00007fff5fbfd930 rsp: 0x00007fff5fbfd918
r8: 0x0000000000000000 r9: 0x00000001001fc0a4 r10: 0x000000000000000f r11: 0x0000000000000000
r12: 0x0000000100110ff0 r13: 0x0000000000000000 r14: 0x000000015b9517fa r15: 0x0000000000000001
rip: 0x0000000000000000 rfl: 0x0000000000010206 cr2: 0x0000000000000000

---

In the snippet above the the interesting part is the stack trace for Thread 0 (the thread that crashed). There is no Sophos-specific code in that trace, in fact it appears to be the operating system loader (dyld) that has crashed. Could be bad memory (memory getting corrupted due to h/w issues, leading to a segfault crash) or could be bad software that is randomly misbehaving. Your previous post suggested other apps crashing, does their strack trace look similar? If so, you have a general system problem. Our software is just a victim of some other fundemental problem.