Bug 14878
| Summary: | r24843 introduces a crash on calling fork() | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Rosyna <webkit-bugs> |
| Component: | JavaScriptCore | Assignee: | 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 | ||
Rosyna
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
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.
Mark Rowe (bdash)
<rdar://problem/5385145>
Mark Rowe (bdash)
Fixed in r24868.