This causes the CallFrame's bytecodeOffset to not be properly set when we enter, e.g., cti_optimize from an op_enter.
This isn't currently a big deal since cti_optimize takes the bytecode offset as its argument, but it will be important for bytecode-liveness-based JSStack scans for GC.
Created attachment 207285 [details]
Comment on attachment 207285 [details]
Clearing flags on attachment: 207285
Committed r153097: <http://trac.webkit.org/changeset/153097>
All reviewed patches have been landed. Closing bug.