Closed Bug 622265 Opened 14 years ago Closed 13 years ago

JM: Incorrect error message from (b.y++) when b is undefined

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- .x+

People

(Reporter: gkw, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: testcase) 

try {
    b.y++
} catch(e) {
    print('' + e)
}
var b

without -m outputs:

TypeError: b is undefined

-m outputs:

TypeError: b.y is undefined

(occurs on both opt and debug shells when passed in as a CLI argument.)

Occurs on TM changeset 8dc385ffb820
This bug goes back to the early days of JM (before bug 578245, at least).
blocking2.0: --- → ?
Summary: JM: Different output with testcase involving print, try...catch → JM: Incorrect error message from (b.y++) when b is undefined
Interp: TypeError: b is undefined
JM: TypeError: b is undefined
JM+TI: TypeError: b is undefined
d8: TypeError: Cannot read property 'y' of undefined
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.