Closed
Bug 61766
Opened 24 years ago
Closed 24 years ago
RegExp with flag explicitly set to undefined causes segfault
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: pschwartau, Assigned: rogerl)
References
Details
RegExp('matchthis', undefined); RegExp('matchthis', 'undefined'); var re = new RegExp('matchthis', undefined); var re = new RegExp('matchthis', 'undefined'); All of these currently cause a segfault in JS Engine. My understanding is that per ECMA, passing undefined as the 2nd parameter should be equivalent to not providing the parameter at all. I don't know about passing the string 'undefined' - it seems to me it should be treated as an invalid flag value (e.g. like passing 'a' as a flag). Or should it be the same as passing the value undefined? At any rate, it shouldn't segfault -
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•24 years ago
|
||
Generated a meta bug to capture all current R.E. bugs.
Assignee | ||
Comment 2•24 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 3•24 years ago
|
||
Verified Fixed - ran this test suite directory on Linux, WinNT, and Mac js/tests/ecma_3/RegExp/ with both debug and optimized versions of the JS shell, and got 0 errors.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•