If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

RESOLVED WORKSFORME

Status

()

Core
JavaScript Engine
RESOLVED WORKSFORME
7 years ago
6 years ago

People

(Reporter: gkw, Unassigned)

Tracking

(Blocks: 2 bugs, {testcase})

Trunk
x86
Mac OS X
testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(blocking2.0 .x+)

Details

(Reporter)

Description

7 years ago
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
Blocks: 622261

Comment 1

7 years ago
This bug goes back to the early days of JM (before bug 578245, at least).
(Reporter)

Updated

7 years ago
blocking2.0: --- → ?

Updated

7 years ago
Summary: JM: Different output with testcase involving print, try...catch → JM: Incorrect error message from (b.y++) when b is undefined
blocking2.0: ? → .x
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
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.