Closed
Bug 891775
Opened 12 years ago
Closed 12 years ago
Differential Testing: Different error message involving try... catch
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: gkw, Unassigned)
Details
(Keywords: testcase)
function f() {
[][""][""]
}
for (a in [0, 0, 0]) {
try {
f()
} catch (e) {
print('' + e)
}
}
shows the following on a 64-bit debug js shell on m-c rev d87b950c7a6f:
TypeError: [][''] is undefined
TypeError: [][''] is undefined
TypeError: [][''] is undefined
but shows the following with --ion-eager:
TypeError: [][''] is undefined
TypeError: [][''] is undefined
TypeError: [][''][''] is undefined
This seems to be an old bug. Setting needinfo for jandem as this may cloud other correctness bugs.
Flags: needinfo?(jdemooij)
Comment 1•12 years ago
|
||
Gary this works for me with a more-determinstic shell. With and without --ion-eager:
TypeError: undefined has no properties
TypeError: undefined has no properties
TypeError: undefined has no properties
Unfortunately, different error messages with "normal" shells is expected due to the way the decompiler and IonMonkey work.
Flags: needinfo?(jdemooij) → needinfo?(gary)
![]() |
Reporter | |
Comment 2•12 years ago
|
||
Argh, I must have found something but used the wrong shell to reduce. I'm pretty sure there still are differential testing errors though, will file new bugs for those.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(gary)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•