-
Notifications
You must be signed in to change notification settings - Fork 236
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
SIGSEGV in fxRunID in xsnap when running ses test-global-object-mutability.js test #627
Comments
@dckc - thanks for writing this up separately. That backtrace has nearly all of our favorite things: Promise, Reflect, async functions, eval, and Proxy. ;) Do you happen to know if this issue happen reliably across your development systems? |
Yes, I just tried it on one other machine (AMD Opteron(tm) Processor 6128 HE w 32GB RAM) and it fails there too. |
Trace info (using 1032135 is a line number from
|
oh! nice to see you've got a fix I can try. Unfortunately, adding a label doesn't notify me. In the future, please add a comment and/or tag @dckc when you have something for me to verify. |
fix confirmed. Thanks!
|
Steps to Reproduce
https://gist.github.com/dckc/19451649697bb7cb231ab5a776fde0d1 has a
Makefile
that automates these steps as well as a transcript of a run and a backtrace:yarn; yarn build
yarn test:xs --debug test/test-global-object-mutability.js
--debug
is optional; it crashes either way. But--debug
gives a useful backtrace.Error#1: test-global-object-mutability.js exited due to signal SIGSEGV
core
file shows that it crashed at xsRun.c:4065 in fxRunIDBuild environment: Linux
Target device: agoric xsnap in the endo repo
Other information
This is using the current moddable SDK 0b451c9
I noted this in #604 (comment) but this looks like a separate issue from #604 .
The ses test is test-global-object-mutability.js.
Getting the SES test suite to run on XS is endojs/endo#508 .
The text was updated successfully, but these errors were encountered: