-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
Strangeness in error message when node gives call stack, if error had occured in specially declared function #8322
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
Comments
A bit fuller example:
|
@vkurchatkin, should I report this to V8 now? |
@nickkolok can you try with the v6.5.0 and see if you can reproduce? v5.x hit end of life a few months ago. |
@evanlucas I'd be be glad if you helped me to install it on Ubuntu 12.04. |
I've seen all sorts of weird stack traces before. |
This is a V8 issue, not something we have direct control over. Can you report it here: https://bugs.chromium.org/p/v8/issues/list? Thanks. FWIW, the output doesn't seem unreasonable to me given the constraints. The function has no name so V8 tries to infer one from context. If you write it like |
MWE:
The strangeness is
at Object.obj.a.obj.b (repl:1:34)
Pure MWE JS:
Is it an error?
If the same object is declared in another way, everything is OK:
The text was updated successfully, but these errors were encountered: