Currently, in the bytecode for a function, we push a JSNamedScope for the name of the function when a debugger is attached. The name scope for the function name is only needed for evals which can redefined the name to resolve to something else, and can later delete the redefined name which should revert the resolution of the name to the original function. The debugger does not add the need for this functionality. Hence, we can remove the presence of the debugger as a criteria for pushing the JSNameScope.
Created attachment 222859 [details] the patch.
Comment on attachment 222859 [details] the patch. View in context: https://bugs.webkit.org/attachment.cgi?id=222859&action=review r=me > Source/JavaScriptCore/ChangeLog:10 > + the function name is only needed for evals which can redefined the name "redefine" > Source/JavaScriptCore/ChangeLog:14 > + The debugger does not add the need for this functionality. Hence, we can > + remove the presence of the debugger as a criteria for pushing the The reason the debugger doesn't need this feature is that it declares all new vars in a temporary, nested scope.
Thanks. Landed in r163210: <http://trac.webkit.org/r163210>.