Bug 169237
| Summary: | The SamplingProfiler should do a sanity check on the callFrame pointer when walking the stack. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mark Lam <mark.lam> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | mark.lam, saam |
| Priority: | P2 | ||
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Mark Lam
This is needed if the profiler gets the callFrame pointer from vm.topCallFrame. If topCallFrame is stale, it may point to un-initialized memory, and the previousCallFrame pointers it gets from there may be invalid.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |