Basically, I was able to come up with a prototype, but needed to patch miden-vm, miden-base, miden-client, miden-node and miden-debug, so the branches are:

https://github.com/walnuthq/miden-base/tree/pr/enable-tx-debugging
https://github.com/walnuthq/miden-client/tree/pr/enable-tx-debugging
https://github.com/walnuthq/miden-debug/tree/pr/enable-tx-debugging
https://github.com/walnuthq/miden-node/tree/pr/enable-tx-debugging
https://github.com/walnuthq/miden-vm/tree/pr/enable-tx-debugging

Please make sure that all of these are using local miden-vm, which is based on next branch, so projects like miden-base, miden-client, miden-node are ported to the new API.

Also, please make sure that it depends on #30 -- the debugger needs to be ported to the new vm as well.

But basically, use case would be:

terminal 1: from miden-node

cargo run --bin miden-node -- bundled bootstrap \
    --data-directory /tmp/miden-node-data \
    --accounts-directory /tmp/miden-node-accounts \
    --genesis-config-file crates/store/src/genesis/config/samples/01-simple.toml
cargo run --bin miden-node -- bundled start \
    --data-directory /tmp/miden-node-data \
    --rpc.url http://localhost:57291

terminal 2: from miden-client

 ./target/debug/miden-client init --network http://localhost:57291
  ./target/debug/miden-client new-wallet
  ./target/debug/miden-client sync
  ./target/debug/miden-client exec \
    --script-path examples/test_debug.masm \
    --start-debug-adapter localhost:4711

terminal 3: from miden-debug

./target/debug/miden-debug --dap-connect localhost:4711

and it will run TUI in the DAP mode.

cc @bitwalker @greenhat

Enable debugging code in the client #29

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions