Bug 1521939 Comment 28 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

The above evidence seems to point at either an entry or exist stub; it seems like we could narrow in pretty quickly by:
 1. confirming issue fixed if all optimized entry/exist stubs disabled (so we go through C++ both dirs)
 2. selectively disabling stubs based on env-var [low,high] func index bounds
 3. bisecting on that to find the individual import/exit stub at fault
The above evidence seems to point at either an entry or exit stub; it seems like we could narrow in pretty quickly by:
 1. confirming issue fixed if all optimized entry/exist stubs disabled (so we go through C++ both dirs)
 2. selectively disabling stubs based on env-var [low,high] func index bounds
 3. bisecting on that to find the individual import/exit stub at fault
The above evidence seems to point at either an entry or exit stub; it seems like we could narrow in pretty quickly by:
 1. confirming issue fixed if all optimized entry/exist stubs disabled (so we go through C++ both dirs)
 2. selectively enabling stubs based on env-var [low,high] func index bounds
 3. bisecting on that to find the individual import/exit stub at fault

Back to Bug 1521939 Comment 28