We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We currently support uploading a file in two places:
Instead, there should only be one option to upload a file and we should auto-detect if it's a JSON test file or PVM program (decodeStandardProgram).
decodeStandardProgram
The file should also be validated before being imported:
Over time uploading binary files will be much more common so it should be a more streamlined input method.
The text was updated successfully, but these errors were encountered:
Jam Service (1).pvm.zip
Here is a file in the SPI format (coming from paritytech/polkavm#190) that can be loaded now in the debugger (using RAW Bytecode tab).
RAW Bytecode
However it seems that from the SPI we only use the raw program code and we don't use it to initialize the memory.
The file should most likely be just passed directly to resetJAM function of a PVM: #132 and we should let the PVM initialize itself.
resetJAM
Sorry, something went wrong.
No branches or pull requests
We currently support uploading a file in two places:
Instead, there should only be one option to upload a file and we should auto-detect if it's a JSON test file or PVM program (
decodeStandardProgram
).The file should also be validated before being imported:
Over time uploading binary files will be much more common so it should be a more streamlined input method.
The text was updated successfully, but these errors were encountered: