Hello,
I am evaluating a bug localisation technique with a repository (http://
www.st.cs.uni-saarland.de/ibugs/) that traced bugs within rhino. So
the versions of rhino i am using are not current ones, but some older
commits, where known bugs are present.
I have been instrumenting those versions (with aspectj) to generate
call-graphs during a run. I am using rhino exclusively with the tools-
shell: a) interactive scripting (just for test purposes) and b) to run
the tests.
A usual run starts with org.mozilla.javascript.tools.shell.Main.main
(String [] args). During interactive scripting the program exits quite
rough when you say js> quit(). That leads to a call to
org.mozilla.javascript.tools.shell.Global.quit which calls System.exit
(); Passing a js-file to the shell ends with simply finishing
org.mozilla.javascript.tools.shell.Main.main(String [] args) (just
like it is supposed to do). Guess you knew that...
Everytime the execution of this main is finished, I am writing a
Object (representing a call-graph) to disk. After a run of /tests/
jsDriver.pl (executing all tests) I realized that there are less
Objects than test files.
It seems as if tests that end with a '-n' (e.g. tests\ecma\Statements
\12.6.3-5-n.js) dont finish their run as usual. The last executed
methods here are:
...
org.mozilla.javascript.Context.exit(..)
org.mozilla.javascript.Context.getCurrentContext(..)
After a long explaination, here finally my questions come:
1) Does that '-n' in a test file name indicate anything? Like 'This
test does NOT what you suppose'... (So what should I expect from those
tests?)
2) I am right that not each run has to end with either:
a) the end of org.mozilla.javascript.tools.shell.Main.main
b) a call to org.mozilla.javascript.tools.shell.Global.quit
Hope someone knows what i am looking for...
Greetings,
Chris
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
