[Webkit-unassigned] [Bug 65399] StackBounds checker fails on custom stack implementations (typically in a coroutine setting)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 1 10:37:45 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=65399





--- Comment #6 from Oliver Hunt <oliver at apple.com>  2011-08-01 10:37:44 PST ---
One problem with this approach is that it assumes a single stack is used per context, which is not the case for JSC -- a single JSC context can be used on multiple threads (just not concurrently), so setting the stack bounds for a "context" doesn't necessarily make sense.

That aside, the new function should go into JSContextRefPrivate.h -- very few APIs ever get to go straight into a public header as we require API and ABI stability: once it's public we can't remove it.  Given this change is very specific to your use case I'm dubious as to its wider value.

It seems to me that a better solution would be for JSC to have a mechanism that checked the actual stack extent that it's executing on, rather than requiring developers that are using this technique to jump through hoops to get the correct behavior.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list