Closed Bug 121755 Opened 23 years ago Closed 5 years ago

Large number of |else if| statements causing an error

Categories

(Rhino Graveyard :: Core, defect, P5)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: pschwartau, Assigned: norrisboyd)

Details

I've just added a new regression test, js/tests/js1_5/Regress/regress-96526.js. 
(http://lxr.mozilla.org/mozilla/source/js/tests/js1_5/Regress/regress-96526.js )

This was for bug 96526, a Mac-only bug. It contains one function with
475 |else if| statements in it. In SpiderMonkey, this test passes on WinNT
and Linux, but fails on Mac due to different memory management there.

In Rhino, this test passes for me in my WinNT rhinoi shell, but fails
in the rhino shell:

*-* Testcase js1_5/Regress/regress-96526.js failed:
Expected exit code 0, got 1
Testcase terminated with signal 0
Complete testcase output was:

java.lang.VerifyError: (class: c11, method: call signature: 
(Lorg/mozilla/javascript/Context;Lorg/mozilla/javascript/Scriptab
le;Lorg/mozilla/javascript/Scriptable;[Ljava/lang/Object;)Ljava/lang/Object;) 
Illegal target of jump or branch
       at 
c12.initScript(D:\JS_trunk\mozilla\js\tests\js1_5\Regress\regress-96526.js) 
       at 
c12.exec(D:\JS_trunk\mozilla\js\tests\js1_5\Regress\regress-96526.js)
       at org.mozilla.javascript.Context.evaluateReader(Context.java:778)
       at 
org.mozilla.javascript.tools.shell.Main.evaluateReader(Main.java:317)
       at 
org.mozilla.javascript.tools.shell.Main.processFile(Main.java:308)
       at 
org.mozilla.javascript.tools.shell.Main.processSource(Main.java:247)
       at org.mozilla.javascript.tools.shell.Main.exec(Main.java:106)
       at org.mozilla.javascript.tools.shell.Main.main(Main.java:68)
Exception in thread "main"
Changing priority to P5 based on recent bug triage.
Priority: -- → P5

Closing. Bug management is now done here:
https://github.com/mozilla/rhino

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.