-
Notifications
You must be signed in to change notification settings - Fork 17.4k
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
encoding/gob: stack overflow #10415
Comments
For reference, the test data above is equivalent to the following hex string "1dffd30201010e726563757273697665536c69636501ffd40001ffd4000007ffd40002010000". The exact same panic can be obtained by trying to decode the recursive map or slice in TestRecursive{Map,Slice}Type in encoder_test.go to a nil pointer (i.e. replace &r2 with nil). One suggestion for handling the panic is to stop recursion when wireId == elemId in (*Decoder).decIgnoreOpFor. Support for recursive types was added in c54b5d0. |
Sent https://golang.org/cl/8938, mostly as a better explanation of my previous comment. I'm not claiming this is the best way to solve the underlying problem, so feel free to discard it. |
CL https://golang.org/cl/8942 mentions this issue. |
Hello. When will be the release with this fix? |
Or is there a way to get a Debian package of current Golang snapshot? |
@xaionaro Please don't ask questions on closed issues. Very few people see them. See https://golang.org/wiki/Questions . Thanks. The fix for this issue is in the Go 1.5 release. |
Go 1.6. February. We don't make Debian packages. |
Ok, thanks. |
Run the following program on the following input:
https://drive.google.com/file/d/0B20Uwp8Hs1oCWEs2azE5WlNEQXc/view?usp=sharing
It crashes with:
I am on commit 7c37249
The text was updated successfully, but these errors were encountered: