Fix is already in nashorn repo @
http://hg.openjdk.java.net/nashorn/jdk8/nashorn
changeset: 553:f1fd5f0bc84c
user:attila
date:Mon Sep 16 14:44:20 2013 +0200
summary: 8024846: keep separate internal arguments variable
It'll go into jdk8 main repo and jdk8 early access build
Any possible workaround for now so that I can continue testing with this
huge application?
On 09/14/2013 04:04 PM, A. Sundararajan wrote:
Hi,
Thanks for the simplified test case. Even simpler test is as follows:
function func(obj) {
var arguments = obj;
for (var i in arguments) {
Looks like return obj is treated like an arguments vector, which is not right.
We do a virtual call to getArgument, which is a ScriptObject method with "obj"
as a receiver, which is not guaranteed to work. See bci 48:
public static java.lang.Object
func(jdk.nashorn.internal.runtime.ScriptFunct
Hi,
Thanks for the simplified test case. Even simpler test is as follows:
function func(obj) {
var arguments = obj;
for (var i in arguments) {
}
return obj;
}
I suspect the issue has to do with handling of 'arguments' shadowing by
local var of "magic" arguments. Renaming argum
Hm, I think the mailing list doesn't support attachments. Here is a link
to the file that causes the VerifyError:
http://sincerity.googlecode.com/git/components/plugins/javascript-nashorn/libraries/scripturian/plugins/javascript-nashorn.js
On 09/13/2013 03:38 PM, Tal Liron wrote:
Hi Attila, I a
Hi Attila, I am attaching the file. I didn't attach it originally,
because I thought it would be impossible for you to test: it is normally
run from within an embedded environment based on Scripturian/Sincerity.
However, I am happy say that i tried anyway and the exact same exception
is reprodu
So you have a file named javascript_nashorn.javascript, I presume. Any chance
you can give it to us? We will probably be able to reproduce from it.
Alternatively, try to use "jjs --compile-only ", see if it fails, and
then try to cut it down to a minimal failing version.
Attila.
Sent from my
Thanks. Unfortunately I can't isolate specific JavaScript code in this
instance for you to reproduce, because I'm trying to run a rather large
application that works in Rhino and I don't know what specifically
causes the failure. The stack trace doesn't tell me much, but it might
help you. Woul
