feat(gnovm): enable debugger for gno test

[mvertes]

This change brings interactive debugging to gno tests, using -debug flag.

New debugger commands have also been added:

• next, to step over the next source line
• stepout, to step out of the current function

Usage example, from the clone root dir:

$ go run ./gnovm/cmd/gno test -v -debug  ./examples/gno.land/p/demo/diff -run TestMyersDiff/Case_sensitivity
Welcome to the Gnovm debugger. Type 'help' for list of commands.
dbg> break gno.land/p/demo/diff/diff.gno:60
Breakpoint 0 at gno.land/p/demo/diff gno.land/p/demo/diff/diff.gno:60:0
dbg> c
=== RUN   TestMyersDiff
=== RUN   TestMyersDiff/Case_sensitivity
> diff.MyersDiff() gno.land/p/demo/diff/diff.gno:60:10
     55: //
     56: // Returns:
     57: //   - A slice of Edit operations representing the minimum difference between the two strings.
     58: func MyersDiff(old, new string) []Edit {
     59: 	oldRunes, newRunes := []rune(old), []rune(new)
=>   60: 	n, m := len(oldRunes), len(newRunes)
     61: 
     62: 	if n == 0 && m == 0 {
     63: 		return []Edit{}
     64: 	}
dbg> p oldRunes
(slice[(97 int32),(98 int32),(99 int32)] []int32)
dbg> stack
0	in gno.land/p/demo/diff.MyersDiff
	at gno.land/p/demo/diff/diff.gno:60:10
1	in gno.land/p/demo/diff.
	at gno.land/p/demo/diff/diff_test.gno:176:4
2	in testing.tRunner
	at testing/testing.gno:364:2
3	in testing.(*testing.T).Run
	at testing/testing.gno:171:2
4	in gno.land/p/demo/diff.TestMyersDiff
	at gno.land/p/demo/diff/diff_test.gno:175:3
5	in testing.tRunner
	at testing/testing.gno:364:2
6	in testing.RunTest
	at testing/testing.gno:298:2
dbg>

[Gno2D2]

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: mvertes/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

[codecov]

Codecov Report

Attention: Patch coverage is 69.51220% with 25 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
gnovm/pkg/test/test.go	26.31%	13 Missing and 1 partial ⚠️
gnovm/pkg/gnolang/debugger.go	77.27%	9 Missing and 1 partial ⚠️
gnovm/pkg/repl/repl.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[leohhhn]

Can we also make this work for filetests somehow?

[mvertes]

Can we also make this work for filetests somehow?

If it is about debugging txtar files, that would be achieved by client side remote debugging to be added in gnodev or gnokey, as discussed per #2683.

[thehowl]

If it is about debugging txtar files, that would be achieved by client side remote debugging to be added in gnodev or gnokey, as discussed per #2683.

No, Leon was asking about usage in _filetest.gno files.