You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Choose the tx you want to debug; remember the tx hash, the chain ID, the JSON RPC URL, and the Sourcify URL. If you're testing the first time, we recommend you check out our simbolik-examples repository and start debugging the AMM contract. You can use the tx from my sandbox.
Create a file called .vscode/launch.json and create a debugging configuration with the data from step2. For example:
Navigate to the debugging panel in VSCode and select the debugging configuration in the dropdown at the top-left corner:
The startup process is yet unoptimized and can take up to 20s. You should see a loading indicator at the bottom-right corner:
Please report any issues and feature requests to this repository.
Known Limitations
The contracts SHOULD be compiled without any optimizations, or the "step to next line" feature will be broken broken. The disassembly view and EVM state are unaffected.
The contracts MUST be compilable with solc v0.8.28.
All contracts SHOULD be source code verified, or you can only debug it on the VM level.
Decoding Solidity Variables is still experimental. We try to be very conservative, and in doubt, we rather display "Unaivable" than a possible incorrect variable value. However, until the ETH Debug format lands, our approach is purely heuristic and may fail. Please be cautious!
The text was updated successfully, but these errors were encountered:
The following instructions serve to test the Simbolik+BuildBear integration.
.vscode/launch.json
and create a debugging configuration with the data from step2. For example:The startup process is yet unoptimized and can take up to 20s. You should see a loading indicator at the bottom-right corner:
Known Limitations
The text was updated successfully, but these errors were encountered: