Fix a bug in delete for lookup slots.

Fix a bug in delete for lookup slots.

The function Runtime_LookupContext searches the context chain for a
LOOKUP slot and returns the object holding the slot.  It returned the
global context if the slot was not found or if it was found in a
function's context or arguments object.  This is not the correct
object to use for 'delete'.

Since this lookup function is only ever used when deleting LOOKUP
slots (those that have to go through a with or a scope with eval), it
is simply replaced with a Runtime_DeleteContextSlot function that does
the appropriate thing for all kinds of context lookups.

This fixes Chromium bug 70066.
http://code.google.com/p/chromium/issues/detail?id=70066

Committed: http://code.google.com/p/v8/source/detail?r=6442

[Mads Ager (chromium), 2011-01-24 13:15:19]

LGTM

http://codereview.chromium.org/6280013/diff/1/src/runtime.cc
File src/runtime.cc (right):

http://codereview.chromium.org/6280013/diff/1/src/runtime.cc#newcode7069
src/runtime.cc:7069: // If the slot was found in a context, it should be
DONT_DELETE.
Can we assert that this is always the case or is that just always implicitly the
case?