-
Notifications
You must be signed in to change notification settings - Fork 386
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
gnovm/pkg/transpiler: mangled imports in Gno code cause a panic when generating Go code #3425
Labels
🐞 bug
Something isn't working
Comments
odeke-em
changed the title
gnovm/pkg/transpiler: mangled imports in Gno code cause a panic when generating Go code
gnovm/pkg/transpiler: mangled imports in Gno code cause a panic and hung the process when generating Go code
Dec 29, 2024
odeke-em
changed the title
gnovm/pkg/transpiler: mangled imports in Gno code cause a panic and hung the process when generating Go code
gnovm/pkg/transpiler: mangled imports in Gno code cause a panic when generating Go code
Dec 30, 2024
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Jan 8, 2025
Adds a fuzzer for Transpile, which found bugs: * gnolang#3425 * gnolang#3426 * partially gnolang#3428 Updates gnolang#3087
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Jan 8, 2025
Adds a fuzzer for Transpile, which found bugs: * gnolang#3425 * gnolang#3426 * partially gnolang#3428 Updates gnolang#3087
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Jan 8, 2025
Adds a fuzzer for Transpile, which found bugs: * gnolang#3425 * gnolang#3426 * partially gnolang#3428 Updates gnolang#3087
odeke-em
added a commit
to odeke-em/gno
that referenced
this issue
Jan 8, 2025
Adds a fuzzer for Transpile, which found bugs: * gnolang#3425 * gnolang#3426 * partially gnolang#3428 Updates gnolang#3087
n2p5
added a commit
that referenced
this issue
Jan 9, 2025
Adds a fuzzer for Transpile, which found bugs: * #3425 in which this following Go program crashed the transpiler ```go package A import(""//" ""/***/) ``` * #3426 which generated an input that revealed the fact that Gno deviates from Go by allowing unused variables yet Go's standard is strict on unused variables like this program ```go package main func main() { const c1 = 1 < 8 main() 1 } ``` which we shouldn't allow * partially #3428 which revealed the discrepancy in Gno that the overflow detection is still lacking as the following program is invalid Go but Gno allowed it to run ```go package main func main() { const c1 = int8(1) << 8 println(c1) } ``` because 1<<8 (256) is higher than the range of int8 for which the maximum is `(1<<7) - 1 aka 127` Updates #3087 Co-authored-by: Nathan Toups <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In furtherance of #3087, I am fuzzing and investigating the transpiler and when presented with this Gno program
Passing it into the transpiler results in this panic
where it tried to generate this Go code
Expected behaviour
Not a panic
Kindly cc-ing @petar-dambovaliev @moul @jaekwon
The text was updated successfully, but these errors were encountered: