-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
segfault with shared builtin #46235
Comments
Related to the work that was done on this pull request cc @addaleax @nodejs/startup |
addaleax
added a commit
to addaleax/node
that referenced
this issue
Jan 18, 2023
Using simdutf during startup can fail when compilation units are linked in the wrong order by a static initialization order issue. nodejs#46235 would also solve this, but since that is a larger effort, this patch focuses on solving the immediate problem. Alternatively, simdutf should arguably be made usable during static initialization, but that is also not as straightforward as this patch. Fixes: nodejs#46235
addaleax
added a commit
to addaleax/node
that referenced
this issue
Jan 18, 2023
Using simdutf during startup can fail when compilation units are linked in the wrong order by a static initialization order issue. nodejs#46235 would also solve this, but since that is a larger effort, this patch focuses on solving the immediate problem. Alternatively, simdutf should arguably be made usable during static initialization, but that is also not as straightforward as this patch. Fixes: nodejs#46235
See #46256 – unfortunately it seems like simdutf is subject to the static initialization order fiasco… |
Closing this issue, since simdutf pull request is merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
20.0.0-pre 15d673d
Platform
linux
Subsystem
builtins
What steps will reproduce the bug?
Build HEAD with
--shared-builtin-cjs_module_lexer/lexer-path=
pointing to a valid file path.Run node without options.
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
No response
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: