Summary: | VM::topCallFrame should be a void* because it may not point to a CallFrame | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Filip Pizlo <fpizlo> | ||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | commit-queue, karim, keith_miller, mark.lam, msaboff, saam | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Bug Depends on: | 160438 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Filip Pizlo
2016-08-01 20:52:14 PDT
Created attachment 296331 [details]
Patch
Comment on attachment 296331 [details]
Patch
I'm not sure that this is the right fix. Is there any reason why we need to populate topCallFrame with topVMEntryFrame?
Comment on attachment 296331 [details]
Patch
r- because all the bots are red. The patch fails to build.
|