-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault #4752
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
Do we have dynamic |
No dynamic import(...) in code. Is there any method to print detail error message or execution stack? |
@feirpri what's the system and version in your qemu env? |
CentOS Linux release 7.7.1908 (Core) |
@feirpri It's a known issue in rust: rust-lang/rust#91979 |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the bug
I got Segmentation fault when i use '@swc/core'
Input code
Config
No response
Playground link
No response
Expected behavior
build successfully
Actual behavior
{
version: '1.2.189',
plugins: [Function: plugins],
Compiler: [class Compiler],
parse: [Function: parse],
parseSync: [Function: parseSync],
parseFile: [Function: parseFile],
parseFileSync: [Function: parseFileSync],
print: [Function: print],
printSync: [Function: printSync],
transform: [Function: transform],
transformSync: [Function: transformSync],
transformFile: [Function: transformFile],
transformFileSync: [Function: transformFileSync],
bundle: [Function: bundle],
minify: [Function: minify],
minifySync: [Function: minifySync],
__experimental_registerGlobalTraceConfig: [Function: __experimental_registerGlobalTraceConfig],
getBinaryMetadata: [Function: getBinaryMetadata],
DEFAULT_EXTENSIONS: [
'.js', '.jsx',
'.es6', '.es',
'.mjs', '.ts',
'.tsx'
]
}
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
Version
1.2.189
Additional context
No response
The text was updated successfully, but these errors were encountered: