Replies: 2 comments 2 replies
-
@1Mateus Thanks for a great description of the problem! Could I ask you to change to
Without looking at the Gramine logs, I can't say why you see SIGSEGV. (Also IIUC Rust's |
Beta Was this translation helpful? Give feedback.
-
Thanks for the logs and experiments! I think we have our suspect:
(same for other logs that you showed) Gramine does not implement It looks like whatever Rust crate you're using ( |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, I'm working with Gramine on a project where we're running a Node.js instance that executes some binaries that were built using Rust.
heres the manifest: https://github.com/hack-a-chain-software/bazk/blob/main/packages/gramine/bazk-build/bazk.manifest.template
We use Node.js to execute some binaries that were built with Rust:
https://github.com/hack-a-chain-software/bazk/blob/main/packages/gramine/src/index.ts#L177
I can correctly compile the binaries and launch the enclave:
When i send a command to execute the 'new_constrained' binary, it executes correctly: https://github.com/hack-a-chain-software/phase2-bn254/blob/feat/gramine/powersoftau/src/bin/new_constrained.rs#L12
But, when I send a command to execute the 'new' binary: https://github.com/hack-a-chain-software/phase2-bn254/blob/feat/gramine/phase2/src/bin/new.rs#L9
I receive this error:
Signal: 'SIGSEGV'
I add logs inside the binaries and discovered that the process fails when this function inside the 'new' command binary tries to execute a new worker: https://github.com/hack-a-chain-software/phase2-bn254/blob/feat/gramine/phase2/src/parameters.rs#L238
thanks for help.:
Beta Was this translation helpful? Give feedback.
All reactions