So maybe 10.14.4 corrupted the filesystem somehow, let's run First Aid.įirst Aid reports some directory failed checks that it is not able to solve. Upgrading to Mojave 10.14.5 does not solve the iTunes crash. Glancing through hoakley's MacOS 10.14.4's known bug list, it seems there are some that have issues with the APFS file system. Spolier alert, uninstalling MalwareBytes does not solve the issue. Could it be that MalwareBytes is attempting to ' scan' iTunes and causes it to crash? My suspicion starts to go to any recently installed apps that might conflict with iTunes, I have recently installed MalwareBytes after the busy month of June Malware festival that was happening. Now what is iTunes trying to copy and failing? Now _platform_strlcpy is darwin's strlcpy C function which ( you guessed it) copies a string. I delete the /Library/Application Support/MobileSync/Backup symlink just to be sure. Maybe some folder structure changed or the symlink broke for some reason (drive name change, etc.). Seems that iTunes is trying to access something it's not supposed to?įirst thing comes to suspicion is the symlink. Termination Reason: Namespace SIGNAL, Code 0xa

Path: /Applications/iTunes.app/Contents/MacOS/iTunesĮxception Codes: KERN_PROTECTION_FAILURE at 0x000070000e218ff8 Looking at the crash report doesn't give you a hint right away. I restart the Mac, start clean, no open apps and let's see. I use a symlink approach to point my Backup folder to an external HDD.įirst thing I try: as they always say, have you tried turning it off and on again?. Now to give some context on my setup, since I'm using a 128GB iPhone, it's not the best use of storage to backup this mammoth on the primary SSD. Trying a couple of times, but still failing, crashes right before I try to do a backup. It turns out iTunes is instantly crashing when I try to do a backup. The control flow stops at the instruction that triggers the exception and does not jump to the sa_handler I installed earlier even I tried command c.On a regular Friday afternoon, I pop in my iPhone to do the regular iTunes backup ( like any sane person does).

lldb seems not being able to ignore any exceptions even I set proc hand -p true -s false SIGSEGV

The program works fine, but the problem is I can't debug it with lldb. Run a code snippet from user and get ready to catch signals/exceptions at any time. I am writing a program on Mac OSX depending on the sigaction/sa_handler mechanism.

Exc_bad_access outlook mac