Status: Accepted Owner: [email protected] Labels: Type-Bug Priority-Medium
New issue 394 by [email protected]: Assessors on global object not handled correctly http://code.google.com/p/v8/issues/detail?id=394 After changing the representation of the global object the handling of accessors is broken. The following code hits an ASSERT in debug mode: x=1 x=1 __degineGetter__('x',function(){}} x=1 x Changing __defineGetter__ to __defineSetter__ causes the same problem. This is caused by the global store inline cache writing directly into the global object property cell. After creating a JavaScript getter or setter the cell will contain a fixed array with two elements containing the getter and/or setter functions. This fixed array is overwritten by the store causing the global object load in the runtime system to fail. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
