Something in r24843 makes fork() call a NULL function pointer and then crash. This happens if the app that hosts WebKit calls fork() for whatever reason. This is a problem because I enjoy calling fork() often. Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 <<00000000>> 0x00000000 0 + 0 1 libSystem.B.dylib 0x900323cc fork + 44
Fork you! The issue here is that I left some of the "unused" malloc zone functions nulled out. Looks like they're not unneeded after all :) The fix here is to provide no-op stubs rather than leaving the function pointers null.
<rdar://problem/5385145>
Fixed in r24868.