Must-fix, thanks for reporting this. /be
Created attachment 159485 [details] [diff] [review] proposed fix Old jsexn.c code (not mine) was too trusting about the values of read/write Error properties such as name and message, leading to stack overflow. Alas, ECMA-262 Edition 3 leaves Error.prototype.toString completely up to the implementation to define. This patch avoids recursive divergence and useless results, but may result in an exception object converting to the empty string, if you set both name and message to non-string or empty-string values. If anyone has a better idea for how Error.prototype.toString should work, feel free to file an RFE. /be
Comment on attachment 159485 [details] [diff] [review] proposed fix Cool, but you gotta add a test!
Comment on attachment 159485 [details] [diff] [review] proposed fix Fixed on trunk; self-approving for branches. /be
Fixed all over the place. /be
Heh. It's funny to hear you ask for permission for two lines of code. Need a license? Do whate'er you want with the code, just don't sue me ;-) I guess that would make it an MIT license. BTW, who is QA? I guess per the workflow they are supposed to "Mark bug as Verified." I'm new to bugzilla.
js1_5/Regress/regress-260541.js checked in.