Bug 14878

Summary: r24843 introduces a crash on calling fork()
Product: WebKit Reporter: Rosyna <webkit-bugs>
Component: JavaScriptCoreAssignee: Mark Rowe (bdash) <mrowe>
Status: RESOLVED FIXED    
Severity: Normal CC: mrowe
Priority: P2 Keywords: InRadar
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   

Description Rosyna 2007-08-03 14:26:13 PDT 
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
Comment 1 Mark Rowe (bdash) 2007-08-03 14:29:16 PDT 
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.
Comment 2 Mark Rowe (bdash) 2007-08-03 14:43:23 PDT 
<rdar://problem/5385145>
Comment 3 Mark Rowe (bdash) 2007-08-04 02:02:50 PDT 
Fixed in r24868.