We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found this in the tests of an old version of go.crypto:
mwhudson@glamdring:~$ cat repro.go package main import "text/template" var tmpl template.Template func main() { tmpl.Parse("") } mwhudson@glamdring:~$ go version go version devel +348f191 Tue Jun 16 10:43:54 2015 +1200 linux/amd64 mwhudson@glamdring:~$ go run repro.go panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0 pc=0x468f41] goroutine 1 [running]: text/template.(*Template).Parse(0x642a60, 0x0, 0x0, 0x7f8a9d0d00a8, 0x0, 0x0) /opt/opensource/go/src/text/template/template.go:180 +0x361 main.main() /home/mwhudson/repro.go:8 +0x2f exit status 2 mwhudson@glamdring:~$ ~/go1.4/bin/go run repro.go
The text was updated successfully, but these errors were encountered:
It fails trying to lock the mutex added by https://go-review.googlesource.com/10101, but this is actually a consequence of https://go-review.googlesource.com/10240 ... The behavior has clearly changed, but is calling Parse on a uninitialized Template legit?
Sorry, something went wrong.
See #11379
No branches or pull requests
I found this in the tests of an old version of go.crypto:
The text was updated successfully, but these errors were encountered: