From Ignacio Grande on golang-nuts,
On Go 1.3rc1, ARM + profiling yields:
unexpected return pc for fmt.(*ss).doScanf called from 0x1
"To reproduce the steps I simply compile it and execute it with no arguments. In a
few seconds you should see some of those unexpected errors on screen, mixed with the
Count messages."
Repro code & data: https://db.tt/ogMKqKi5
I confirmed this behavior with Go tip (b476a7d) on a Chromebook with a Debian chroot.
Code, for easier linking is: http://play.golang.org/p/JSdMUdGIrW
No unsafe, no races (no goroutines).
