by guohouzuo:

What steps will reproduce the problem?

Sorry! I have not been able to make a small & reproducible example. See additional
information below.

Which compiler are you using (5g, 6g, 8g, gccgo)?

Golang 1.2, downloaded and compiled by Homebrew

Which operating system are you using?

OSX Mavericks, Darwin 13.0 64-bit

Which version are you using?  (run 'go version')

go version go1.2 darwin/amd64

Please provide any additional information below.

In the middle of debugging a performance issue in my project tiedot, I turned on CPU
profiling (runtime/pprof), and the segmentation fault happens at a very small chance.
The stack trace of fault is:

SIGSEGV: segmentation violation
PC=0x1e382

acquirep(0x0)
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/proc.c:2273 +0x52
stopm()
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/proc.c:940 +0x157
findrunnable()
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/proc.c:1237 +0x42d
schedule()
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/proc.c:1320 +0xe3
park0(0x22663d5a0)
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/proc.c:1361 +0xd8
runtime.mcall(0x29af2)
    /usr/local/Cellar/go/1.2/libexec/src/pkg/runtime/asm_amd64.s:178 +0x4b

Complete stacktrace of all dumped goroutines is attached.

Attachments:

1. complete_goroutine_trace (25285 bytes)