Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test262Error objects have no stack trace #1230

Closed
thejoshwolfe opened this issue Sep 18, 2017 · 0 comments
Closed

Test262Error objects have no stack trace #1230

thejoshwolfe opened this issue Sep 18, 2017 · 0 comments

Comments

@thejoshwolfe
Copy link
Contributor

(Tested in v8.)

When an assertion throws a Test262Error, there's no stack trace printed. If I change the assert implementation to throw an Error instead, I get a stack trace as expected.

I understand that a stack trace is not part of the ecma262 spec, so it's not a primary concern for test262, but it would be nice.

I played around with making a pull request that fixes this issue, but it seems pretty difficult to get this to work without mentioning any implementation-specific stack field and without using ES6 classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants