Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
What steps will reproduce the problem? 1. Run http://play.golang.org/p/uMX6Y4ndl9 What is the expected output? panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x28 pc=0x400cfc] ... What do you see instead? %v(PANIC=runtime error: invalid memory address or nil pointer dereference) Which operating system are you using? Linux Which version are you using? (run 'go version') 8g version go1.0.1 8g version weekly.2012-03-27 +95456588a8e1
It is intentional that fmt turns panic while evaluating arguments into a descriptive string. That is usually more useful than not printing anything and triggering a backtrace, especially when the print is already trying to report an error. I suppose we could change the message used in the panic to include the pc. It will never include a full trace as in your expected output.
Status changed to Thinking.