-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
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
Gno crashes with a runtime panic if a type declaration has a selector expression but Go reports an invalid type at compile type #3712
Labels
Comments
odeke-em
changed the title
Gno crashes with a runtime panic if a type declaration has a selector expression but Go reports an invalid type
Gno crashes with a runtime panic if a type declaration has a selector expression but Go reports an invalid type at compile type
Feb 9, 2025
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Feb 9, 2025
…ions + expected failures With this change, we enhance the fuzzer with known panic causes but even better by looking at results from Go panicking and raising if there is some discrepancy. This update has helped uncover a couple of bugs like: * gnolang#3712 * gnolang#3713
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Feb 9, 2025
…ions + expected failures With this change, we enhance the fuzzer with known panic causes but even better by looking at results from Go panicking and raising if there is some discrepancy. This update has helped uncover a couple of bugs like: * gnolang#3712 * gnolang#3713
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Feb 9, 2025
…ions + expected failures With this change, we enhance the fuzzer with known panic causes but even better by looking at results from Go panicking and raising if there is some discrepancy. This update has helped uncover a couple of bugs like: * gnolang#3712 * gnolang#3713
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Feb 11, 2025
…ions + expected failures With this change, we enhance the fuzzer with known panic causes but even better by looking at results from Go panicking and raising if there is some discrepancy. This update has helped uncover a couple of bugs like: * gnolang#3712 * gnolang#3713
Thank you for filing this issue. It does not appear to be an exploitable security issue, as it cannot be published to chain: % gnokey maketx addpkg --pkgpath "gno.land/r/kristovatlas/gno3712a" --pkgdir . --gas-fee 10000000ugnot --gas-wanted 800000 --broadcast --chainid dev --remote localhost:26657 Dev
Enter password.
TX HASH:
--= Error =--
Data: invalid gno package; type check errors:
gno.land/r/kristovatlas/gno3712a/gno3712.gno:3:12: int.A0000 is not a type
Msg Traces:
0 redacted/gno/tm2/pkg/errors/errors.go:28 - deliver transaction failed: log:msg:0,success:false,log:--= Error =--
Data: vm.TypeCheckError{abciError:vm.abciError{}, Errors:[]string{"gno.land/r/kristovatlas/gno3712a/gno3712.gno:3:12: int.A0000 is not a type"}}
Msg Traces:
Stack Trace:
...snip... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This code found by fuzzing
In Gno
With https://play.gno.land/p/G8-Hf2OrqDg panics at runtime without a compile failure
In Go
Correctly fails in Go per https://go.dev/play/p/ck3LDvKbLEH with
./prog.go:5:12: int.A0000 is not a type
The text was updated successfully, but these errors were encountered: