Bug 160441

Summary: VM::topCallFrame should be a void* because it may not point to a CallFrame
Product: WebKit Reporter: Filip Pizlo <fpizlo>
Component: JavaScriptCoreAssignee: 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 Flags
Patch mark.lam: review-

Filip Pizlo
Reported 2016-08-01 20:52:14 PDT
Patch forthcoming.
Attachments
Patch (1.13 KB, patch)
2016-12-06 15:07 PST, Karim 		mark.lam: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Karim
Comment 1 2016-12-06 15:07:09 PST
Created attachment 296331 [details] Patch
Mark Lam
Comment 2 2016-12-06 15:12:29 PST
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?
Mark Lam
Comment 3 2016-12-06 19:24:05 PST
Comment on attachment 296331 [details] Patch r- because all the bots are red. The patch fails to build.
Note You need to log in before you can comment on or make changes to this bug.