On Fri, Nov 8, 2013 at 1:10 AM, Uros Bizjak <ubiz...@gmail.com> wrote: > > panic: runtime error: invalid memory address or nil pointer dereference > [signal 0xb code=0x1 addr=0x1c] > > goroutine 5 [running]: > syscall.Exitsyscall > ../../../gcc-svn/trunk/libgo/runtime/proc.c:1986 > pprof.profileWriter > > /home/uros/gcc-build/alphaev68-unknown-linux-gnu/libgo/gotest29851/test/pprof.go:600 > created by runtime_pprof.StartCPUProfile > > /home/uros/gcc-build/alphaev68-unknown-linux-gnu/libgo/gotest29851/test/pprof.go:594 > > goroutine 1 [chan receive]: > testing.RunTests > ../../../gcc-svn/trunk/libgo/go/testing/testing.go:470 > testing.Main > ../../../gcc-svn/trunk/libgo/go/testing/testing.go:401 > main.main > > /home/uros/gcc-build/alphaev68-unknown-linux-gnu/libgo/gotest29851/test/_testmain.go:34 > > goroutine 4 [chan receive]: > pprof_test.testCPUProfile > > /home/uros/gcc-build/alphaev68-unknown-linux-gnu/libgo/gotest29851/test/pprof_test.go:108 > testing.tRunner > ../../../gcc-svn/trunk/libgo/go/testing/testing.go:389 > created by testing.RunTests > ../../../gcc-svn/trunk/libgo/go/testing/testing.go:469 > FAIL: runtime/pprof > gmake[2]: *** [runtime/pprof/check] Error 1 > > This one is new, I have to look into it a bit deeper.
I don't know what is happening here. I can't recreate it. There was a different problem that could arise in runtime/pprof, that was fixed by a patch I submitted on Saturday (http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01016.html). So it's possible that this is fixed now. If you are able to recreate it, try setting GOTRACEBACK=2 in the environment. That will provide more information in the backtrace. Ian
