VM CLI debug sessions #1035

New issue

Open

opened 2025-12-28 17:15:00 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:15:00 +00:00

Owner

Originally created by @AnnaShaleva on GitHub (Nov 28, 2022).

Currently loadnef and loadgo commands perform dynamic script loading which makes subsequent method run fail on notification emission or storage context access (see https://github.com/nspcc-dev/neo-go/pull/2824#issue-1466185629 and https://github.com/nspcc-dev/neo-go/pull/2824#discussion_r1033530726). 6bf9856c16a475961fd3832575f3d01a42967552 is not enough, we need to implement debug sessions to be able to deploy the contract firstly and call its method afterwards.
We also need an ability to perform calls/invoke scripts based on some previous VM state got from other script invocation. It can also be implemented via debug sessions mechanism and it's a useful feature for contract debugging. Requested by @carpawell.

Originally created by @AnnaShaleva on GitHub (Nov 28, 2022). 1. Currently `loadnef` and `loadgo` commands perform dynamic script loading which makes subsequent method run fail on notification emission or storage context access (see https://github.com/nspcc-dev/neo-go/pull/2824#issue-1466185629 and https://github.com/nspcc-dev/neo-go/pull/2824#discussion_r1033530726). 6bf9856c16a475961fd3832575f3d01a42967552 is not enough, we need to implement debug sessions to be able to deploy the contract firstly and call its method afterwards. 2. We also need an ability to perform calls/invoke scripts based on some previous VM state got from other script invocation. It can also be implemented via debug sessions mechanism and it's a useful feature for contract debugging. Requested by @carpawell.